- Home
- Resources
- Integrations
- Contentful
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
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.
How do you connect Contentful to n8n?
- 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.
- 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.
- 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.
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.
Operations index
Asset
2 operationsGet
asset.getWhat 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:
deliveryApireads what is published,previewApireads the draft state, and the choice changes what comes back. - Environment ID: the environment to read, such as
masterorstaging; on plans without environments, usemaster.
Get Many
asset.getAllWhat 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.createdAtto 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.
Content Type
1 operationGet
contentType.getWhat 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:
deliveryApiorpreviewApi, depending on which API your workflow is authenticated against. - Environment ID: lets a workflow check the model on
stagingbefore the same check runs onmaster.
Entry
2 operationsGet
entry.getWhat 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
previewApito inspect an entry still in draft, atdeliveryApifor the live version. - RAW Data: keeps the raw response, useful when a downstream node expects the original structure.
Get Many
entry.getAllWhat 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.createdAtto start from the most recent entries.
Locale
1 operationGet Many
locale.getAllWhat 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
stagingshows up there beforemaster. - Return All: on for the full list; off, Limit decides how many locales the node returns.
- Source:
deliveryApiorpreviewApi, matching the token stored in the credential.
Space
1 operationGet
space.getWhat 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:
deliveryApiorpreviewApi, and running it once against each is a fast way to see which of the two tokens you actually filled in.
Need help automating Contentful with n8n?
A person reads every message.

