n8n + Contentful

Usually just publish and unpublish, filtered to the content types the workflow cares about. Contentful can fire a webhook on every entry save, including the auto-save events that happen repeatedly while an editor is typing, so a webhook subscribed to all entry events can hit n8n dozens of times for a single draft. On self-hosted n8n that is wasted work; on n8n Cloud each of those calls is a billed execution. Set the topics and content-type filters in Contentful's webhook settings rather than filtering inside n8n, so the unwanted events never leave Contentful at all.

Yes, but not through n8n's built-in Contentful node, which only reads: it fetches entries, assets, content types, and locales. Creating or updating entries goes through the HTTP Request node calling Contentful's Content Management API with a management token. That means building the request body yourself, including the per-locale field structure Contentful expects and the entry version number every update must send. It is a one-time setup per workflow, and n8n's credential store keeps the token out of the workflow itself.

Because a workflow that writes back to an entry fires Contentful's webhook again. The classic case is a workflow that listens for entry changes and then fills in a missing SEO field: its own update counts as a change, which starts the workflow again. Three ways out: listen only for publish while the workflow saves without publishing, have the workflow check whether the field is already set before writing, or use a dedicated management token and check who made the change before continuing. Any one of these breaks the loop; the check-before-write guard is the simplest to reason about.

It runs into Contentful's per-second request limit on the Content Management API, and requests over it are rejected with a rate-limit error rather than queued. In n8n, process the entries in small batches with the Loop Over Items node, add a short Wait between batches, and turn on Retry On Fail for the HTTP Request node so an occasional rejection is retried instead of failing the run. Monthly API call quotas matter too on the free plan; the Pricing section covers what each Contentful plan includes.

Both stacks use n8n to react to CMS events; the difference is who runs the CMS. Contentful is a managed service: nothing to host or patch, but the jump from its free plan to the first paid plan is steep, and content lives on Contentful's platform. The n8n + Strapi stack runs an open-source CMS on your own server with PostgreSQL, so the CMS costs a server rather than a subscription and you own the database, at the price of operating it. Pick this stack when a content team is already on Contentful or wants a hosted editor; pick the Strapi variant when self-hosting and cost control matter more. The n8n workflows are similar in shape, but not portable one to one, since the webhook payloads differ.