A webhook is an HTTP request your CMS sends to your server when content changes. In a headless setup it is what connects the editor to everything else: a publish click triggers a site rebuild, a cache purge, a search index update or a message to Slack. If you want a shortlist: Sanity for filtered, shaped payloads, DatoCMS for retries and templates, Hygraph for stage-aware triggers, and Strapi or Directus if you want to host the CMS yourself.
We read each platform’s webhook docs on 27 October 2026 where they were reachable. Where they were not, the entry says so. For the wider market see the headless CMS platform directory and our headless CMS guide.
What should webhooks do in a headless CMS?
Webhooks in a headless CMS do four jobs. They trigger a build or revalidation when a page is published. They invalidate caches. They sync content into other systems such as search or a CRM. And they notify people or services about workflow steps.
The differences between platforms show up in details. Which events exist (publish, unpublish, delete, asset changes, workflow stages)? Can you filter so that a draft save does not fire a thousand builds? Is the payload signed? What happens when your endpoint is down? These are the points we compare.
How we evaluated
We scored platforms on events, filtering and payload control, signing, retries, and hosting. We opened the docs for Sanity, Strapi, DatoCMS, Hygraph, Storyblok, Prismic and Directus, plus Payload’s hooks page. Contentful’s webhook docs returned a rate limit error twice, so its entry is general and flagged.
Webhook comparison table
| Platform | Events and filtering | Signing | Retries | Hosting | Free tier |
|---|---|---|---|---|---|
| Sanity | Create, update, delete, with GROQ filter and projection | Secret signature | 2 retries, 30 seconds apart | SaaS | Yes, 2 webhooks |
| Strapi | Entry, media and release events | Auth headers, HMAC recommended | Build your own | Self-host or cloud | Open source |
| DatoCMS | Record, model, upload and deploy events | Custom headers and basic auth | Up to 7 retries | SaaS | Yes |
| Hygraph | Models, stages and actions | gcms-signature header | Not verified | SaaS | Yes |
| Storyblok | Story, asset, workflow and more | webhook-signature, paid plans | None | SaaS | Yes, 3 webhooks |
| Prismic | Publish, unpublish, releases, tags | Secret field in payload | Not verified | SaaS | Yes |
| Directus | Flows with webhook and event triggers | Your flow logic | Your flow logic | Self-host or cloud | Open source |
| Payload | Server-side hooks in code | Not applicable | Your code | Self-host | Open source |
| Contentful | Webhooks on content changes | Not verified | Not verified | SaaS | Yes |
Sanity
Sanity webhooks fire on create, update or delete, and a GROQ filter decides which documents count. A GROQ projection shapes the JSON, so your endpoint gets only what it needs. You can pick the HTTP method, add headers and sign payloads with a secret. Delivery is at least once, with an idempotency key header for deduplication. Failed requests retry twice, 30 seconds apart. The free plan includes 2 GROQ-powered webhooks and Growth includes 4, as of October 2026. See Sanity development.
Best for: precise, filtered triggers. Skip if: you need many webhooks on the free plan.
DatoCMS
DatoCMS covers record events (create, update, delete, publish, unpublish), model and upload events, and deploy status events. You can write a custom payload with Mustache templates, add headers or basic auth, and rely on up to seven automatic retries from 2 minutes up to 2 days. Timeouts are tight at 8 seconds total, so answer quickly. We found no signature scheme in the docs we read. We have no separate DatoCMS page.
Best for: teams that want retries without building them. Skip if: you need signed payloads.
Hygraph
Hygraph triggers on content models, stages (draft, published or custom) and actions including publish and unpublish. Set a secret and Hygraph sends a gcms-signature header you verify with its utility package. Create, update and delete send the draft; publish and unpublish send the published version. See Hygraph services.
Best for: editorial workflows with stages. Skip if: you need rich retry controls; we did not verify them.
Storyblok
Storyblok has the longest event list we found: stories, assets, workflow stage changes, user management, datasource entries, discussions, releases and pipelines. Paid plans add a secret and a webhook-signature header. Webhooks do not retry on failure, and your endpoint should respond within 120 seconds, using 202 for longer work. The free plan includes 3 webhooks. See Storyblok.
Best for: teams reacting to many event types. Skip if: missed deliveries are unacceptable and you cannot add a fallback.
Strapi
Strapi sends entry events (create, update, delete, publish, unpublish, draft discard) and media events. You set default headers in config, and the docs recommend verifying an HMAC signature in your receiver. Webhooks do not fire for the User type; use lifecycle hooks for that. Review workflow and release events need paid plans. See Strapi development.
Best for: self-hosted control over what fires. Skip if: you need built-in retries.
Directus
Directus uses Flows: a trigger (event hook, webhook, schedule or manual) leads to operations such as a request to a URL. That is more flexible than a fixed webhook list, because you can add conditions, transform data and chain steps. It also means retries and signing are logic you build. See Directus.
Best for: automation beyond simple notifications. Skip if: you want a fixed webhook screen.
Prismic
Prismic fires webhooks when a page is published or unpublished, when a release changes, and when a tag is created or deleted. You can limit triggers, and each payload carries your secret. Manage them in settings or through the CLI. Details on Prismic.
Best for: rebuild-on-publish sites. Skip if: you need payload shaping.
Payload
Payload does not center on outbound webhooks. It gives you server-side hooks such as beforeChange and afterChange in your code, so you can call any URL, queue a job or revalidate a Next.js path yourself. That is flexible and fully testable, and it means you write the delivery logic. See Payload development.
Best for: developer teams who want control and tests. Skip if: editors need to configure webhooks in a UI.
Contentful
Contentful supports webhooks on content changes and is widely used to trigger builds. We could not open its webhook docs today, so we do not state its events, signing or retries. See Contentful.
Best for: established enterprise pipelines. Skip if: you have not checked its current limits.
How to choose
Pick by failure mode. If your endpoint can be down, choose retries (DatoCMS, Sanity) or plan a rebuild schedule. If noisy drafts would flood your build system, choose filters (Sanity) or stage-aware triggers (Hygraph). If you need to chain actions, choose Directus Flows or Payload hooks.
Whatever you pick, return 2xx fast, queue the work, verify signatures and make handlers idempotent. If you want us to design the pipeline or compare options, see our headless CMS agency.