Resources · n8n integration

Contentful n8n integrationAutomate Contentful with n8n.

Your content should not stay stuck behind the Contentful web app. The Contentful n8n integration reads a space from a workflow: 7 operations across 5 resources cover assets, content types, entries, locales and the space itself. Useful for content and ops teams who publish on a rhythm.

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the Contentful n8n integration actually do?

The Contentful node turns a space into something a workflow can read. It ships with n8n, so there is nothing to install on n8n Cloud or on a self-hosted instance, and it authenticates with a Contentful API access token you store once. The catalogue exposes 7 operations spread over 5 resources: Asset, Content Type, Entry, Locale and Space.

The first thing most teams build is a content inventory. Get Many Entries filtered on a content type returns every entry of that model, and the rows land in Google Sheets where an editor can sort them by date and spot what nobody has touched in a year. Because the same workflow can run on a schedule, the sheet rewrites itself without anyone opening Contentful.

Media reviews work the same way, one resource over. Get Many Assets with Return All switched on walks through the whole library page by page, and a short digest of what came back can go straight to Slack for the design channel. Teams that publish a lot of visuals use this to keep the library from quietly filling up.

Translation checks are the third pattern. Get Many Locales lists the locales configured on the space, and a loop over Get an Entry pulls each one back so the workflow can compare them. When something is missing, a message goes out through Gmail to whoever owns that language, with the entry identifier in the body.

Contentful has no trigger node in n8n, so a workflow starts somewhere else: a Schedule Trigger firing at a fixed interval, an n8n Webhook (a URL another service calls) or the trigger of another tool already in your stack. That is a design choice to make early, since it decides how fresh the data in your report is.

Anything that falls outside those 7 catalogue operations goes through the HTTP Request node, which calls any endpoint of the Contentful API while reusing the same credential. The public template 640, Get all the entries from Contentful, is a good starting point if you want to see the node wired up before writing your own. For a wider look at where n8n fits, read the n8n review.

Connect

How do you connect Contentful to n8n?

  1. 01

    Generate the keys in Contentful

    You need a Contentful account and a space before anything else. Open Settings > API keys in Contentful and create a key: the Space ID is shown while the tokens are generated, and the same key produces both a Content Delivery API Access Token and a Content Preview API Access Token. Keep the page open, you will paste all three values into n8n in a moment.

  2. 02

    Store the credential once in n8n

    In n8n, a credential is a saved set of connection details that every workflow can reuse. Go to the Credentials menu, create a Contentful credential and fill the Space ID, the Content Delivery API Access Token and the Content Preview API Access Token. A token field you do not plan to use can stay blank. Once saved, the Contentful node offers this credential in its dropdown.

  3. 03

    Run one read to confirm it works

    Drop a Contentful node on the canvas, pick the credential, and choose Get a Space. It is the shortest round trip: no identifier to supply, just Source. If the space details come back, the token is valid. Then move on to a real operation and set Environment ID, which is the Contentful environment the node reads from, such as master or staging.

Actions

What can the Contentful node do?

The Contentful node exposes 7 operations across 5 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.

Resources × operations matrix
ResourceGetGet Many
Asset✓✓
Content Type✓
Entry✓✓
Locale✓
Space✓

Asset

2 operations
01

Get

asset.get

What you see in n8n

Notes & use cases

Fetches one file already uploaded to a space, identified by hand or by an expression, instead of scanning the whole media library.

Key parameters

  • Asset ID: the identifier of that asset in Contentful, often {{ $json.field }} when a previous node carried it through.
  • Source: deliveryApi reads what is published, previewApi reads the draft state, and the choice changes what comes back.
  • Environment ID: the environment to read, such as master or staging; on plans without environments, use master.
Use cases
a product email workflow that needs one specific image before it hands the payload to the sending tool.
02

Get Many

asset.getAll

What you see in n8n

Notes & use cases

Reads the assets of a space as a list, with search filters, which is how a workflow audits a media library in one run.

Key parameters

  • Return All: on, n8n pages through every asset in the space; off, Limit caps how many come back.
  • Order: sorts the response on a sys property or a field value, for example sys.createdAt to put the newest files first.
  • Fields: a comma separated list of the fields to return, handy when only a title matters downstream.
  • RAW Data: returns the response unparsed, for workflows that prefer to handle the structure themselves.
Use cases
a quarterly sweep of everything uploaded since the last review, dumped into a spreadsheet.

Content Type

1 operation
03

Get

contentType.get

What you see in n8n

Notes & use cases

Returns the definition of one content model, the shape that every entry of that type follows in the space.

Key parameters

  • Content Type ID: the identifier of the model to read, taken from Contentful or passed as an expression such as {{ $json.field }}.
  • Source: deliveryApi or previewApi, depending on which API your workflow is authenticated against.
  • Environment ID: lets a workflow check the model on staging before the same check runs on master.
Use cases
a guard step that reads the model first, so a later mapping does not silently drift when someone edits the structure.

Entry

2 operations
04

Get

entry.get

What you see in n8n

Notes & use cases

Pulls a single piece of content back by its identifier, which is what you want once another step has already told you which entry matters.

Key parameters

  • Entry ID: the identifier of the entry, commonly filled with an expression such as {{ $json.field }} when it comes from a form submission or an earlier read.
  • Source: point it at previewApi to inspect an entry still in draft, at deliveryApi for the live version.
  • RAW Data: keeps the raw response, useful when a downstream node expects the original structure.
Use cases
a review workflow that reads the draft of an article and posts it for approval before anyone publishes.
05

Get Many

entry.getAll

What you see in n8n

Notes & use cases

Queries the entries of a space and returns them as a list, which makes it the workhorse of most Contentful workflows.

Key parameters

  • Content Type ID: restricts the search to entries of one model, so a blog export does not also return landing pages.
  • Query: full text search across the entries, case insensitive, and it needs more than one character to run.
  • Return All: on, every matching entry comes back across as many pages as needed; off, Limit sets the ceiling.
  • Order: sets the order of the response, for example sys.createdAt to start from the most recent entries.
Use cases
a weekly export of published articles into a sheet the editorial team already reviews.

Locale

1 operation
06

Get Many

locale.getAll

What you see in n8n

Notes & use cases

Lists the locales configured on the space, which tells a workflow what languages it is supposed to handle rather than assuming them.

Key parameters

  • Environment ID: locales are read per environment, so a new language added on staging shows up there before master.
  • Return All: on for the full list; off, Limit decides how many locales the node returns.
  • Source: deliveryApi or previewApi, matching the token stored in the credential.
Use cases
the first node of a translation check, feeding the list of locales into a loop that reads each version of an entry.

Space

1 operation
07

Get

space.get

What you see in n8n

Notes & use cases

Returns the space the credential points at. There is no identifier to supply, which makes it the quickest way to prove a connection works before building anything on top of it.

Key parameters

  • Source: deliveryApi or previewApi, and running it once against each is a fast way to see which of the two tokens you actually filled in.
Use cases
a health check at the top of a scheduled workflow, so a broken token surfaces as a clear failure instead of an empty report further down.
Need help

Need help automating Contentful with n8n?

A person reads every message.

FAQ

Contentful and n8n, the usual questions

01Is the Contentful n8n integration free?
Yes on the n8n side. The Contentful node ships with n8n, so there is nothing to install and nothing extra to pay for: it behaves the same on n8n Cloud, the hosted offer run by n8n, and on a self-hosted instance installed through Docker or npm. A workflow built in one runs in the other without changes. What Contentful itself costs on your plan is a separate question and this page does not cover it. The only thing you need from Contentful to get started is an account, a space and an API access token.
02What credentials do you need to connect Contentful to n8n?
One Contentful credential, built from an API access token. In n8n a credential is the saved set of connection details every workflow can reuse, so you enter it once in the Credentials menu and pick it from the node dropdown afterwards. It takes three values: the Space ID, which Contentful displays while you generate the tokens, a Content Delivery API Access Token if you plan to read published content, and a Content Preview API Access Token if you plan to read drafts. You can leave either token blank when you do not intend to use that API. Both are generated together from Settings > API keys in Contentful.
03What are the limits of the Contentful node in n8n?
The node covers 7 operations across 5 resources: Asset, Content Type, Entry, Locale and Space. Anything outside that list goes through the HTTP Request node, which calls any endpoint of the Contentful API and reuses the same credential through predefined authentication, so you are not stuck. On the list operations, watch Return All: leave it off and the node stops at Limit, which is how partial exports end up looking complete. Environment ID matters too, since a read on staging and a read on master can legitimately return different content for the same identifier.
04Can n8n react to a Contentful change in real time?
Not from the Contentful node itself, because this tool has no trigger node in n8n. A workflow that involves Contentful starts somewhere else. The usual option is a Schedule Trigger, which runs the workflow at a fixed interval, every morning or every hour, and then reads the space with Get Many Entries or Get Many Assets. The second option is the n8n Webhook node, a URL that another service calls when something happens on its side, which then kicks off the Contentful read. The third is simply the trigger of another tool already in the workflow.
05n8n or Make for Contentful?
It depends on where you want the automation to live. Make is a hosted automation platform with no self-hosting option, billed per operation, so cost scales with how many steps your scenarios run. n8n can be self-hosted through Docker or npm, or used on n8n Cloud, and the same workflow behaves identically in both. If your content data has to stay on infrastructure you control, self-hosting settles it. If you never want to run a server, the hosted side of either tool works. Look at the cost model and the visual logic you find easier to read, then pick.