Resources · n8n integration

Strapi n8n integrationAutomate Strapi with n8n.

Can a workflow write to your CMS without a single line of glue code? That is what the Strapi n8n integration gives you: one Entry resource, 5 operations that cover create, read, update and delete, and no trigger node, so any schedule or incoming call can start the run.

Try the Strapi integration on n8n See the 5 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the Strapi n8n integration actually do?

The Strapi node talks to the REST API of your Strapi project and works on one object: the entry, a single record inside a collection type. You name the content type, n8n authenticates with a credential you saved once, and the entry comes back as JSON that the next node can read.

The node ships with n8n, on n8n Cloud and on a self-hosted instance alike, so there is nothing to install and nothing extra to pay on the n8n side.

Take a content backlog that fills itself. A Schedule Trigger, the n8n node that runs a workflow at a fixed interval, wakes things up every morning, a row arrives from Google Sheets, and entry.create writes it into your articles collection. Writers keep working in a spreadsheet, the site reads Strapi.

Second pattern: an export that stays current. entry.getAll pulls a whole collection type with Return All switched on, and the items land in Airtable or in a reporting table in Postgres. Nobody copies rows by hand again.

Third pattern: human review before anything goes live. A submission comes in, the workflow posts it to Slack, a reviewer answers, and entry.update writes the verdict back on the matching record. Submissions that fail review go to entry.delete in the same run, so the collection type only ever holds what a person actually approved, and the trace of the decision stays in the execution log.

Now the honest part, because the node stops somewhere. It exposes the Entry resource and nothing else. Anything outside the Entry resource, any other content in your Strapi project or anything a plugin adds on top of the REST API, stays out of reach of the 5 operations, and the credential only targets Version 3 or Version 4 of the API. When you need one of those calls, the HTTP Request node reaches any endpoint of the Strapi REST API and reuses the same credential through its predefined authentication, so you keep one place to store the token.

If the question is the platform rather than the node, the n8n review walks through the trade-offs, and the n8n training covers building these workflows end to end.

Connect

How do you connect Strapi to n8n?

01
Choose between a user account and a token
Strapi credentials support two authentication methods. An API user account uses the Email and Password of an end user, never of an admin account, and inherits that user's content permissions. An API token is created from an admin account, under Settings > Global Settings > API Tokens. Tokens suit a server-to-server workflow; a user account suits a workflow that must stay inside one role's permissions.
02
Give the role its permissions
For the user account route, open Settings > Users & Permissions Plugin, then either extend the default Authenticated role or create a new one. In the Permissions section, open the collection type you plan to automate and tick what the workflow needs: create, find and findone, update, delete. Repeat for every collection type, save the role, then create the end user under Content Manager > Collection Types > User and assign it.
03
Fill the credential inside n8n
In n8n, open Credentials and create a Strapi credential. The URL is the public address of your Strapi server, the url parameter in ./config/server.js; Strapi recommends an absolute URL, and a Strapi Cloud project uses its own address such as https://my-strapi-project-name.strapiapp.com. Pick the API Version, Version 3 or Version 4. The credential is saved once and appears in the dropdown of every Strapi node afterwards.

Actions

What can the Strapi node do in a workflow?

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

Resources × operations matrix
Resource	Create	Get	Get Many	Update	Delete
Entry	✓	✓	✓	✓	✓

Entry

5 operations

Create an entry

entry.create

What you see in n8n

Notes & use cases

Posts a new record into a collection type and returns it, including the id Strapi assigned, which the rest of the workflow can reuse.

Key parameters

Content Type: the name of the content type receiving the record, typed as Strapi exposes it.
Columns: a comma-separated list of the properties to write, in the style of id,name,description. Leave a property out and it never reaches Strapi, even when it sits in the incoming item.

Use cases

a webinar sign-up form feeds the workflow and each answer becomes an entry in a registrations collection type.

Delete an entry

entry.delete

What you see in n8n

Notes & use cases

Removes one record from a collection type. The node returns the deleted record, so later steps still have its content to archive or to announce.

Key parameters

Content Type: the collection type holding the record to remove.
Entry ID: the ID of the entry to delete, usually carried over from a previous node as {{ $json.id }}, an n8n expression that reads a field of the incoming item.

Use cases

a nightly cleanup that clears expired job listings once their closing date has passed.

Get an entry

entry.get

What you see in n8n

Notes & use cases

Reads a single record by its identifier and hands its fields to the next node, without touching anything in Strapi.

Key parameters

Content Type: the content type to read from.
Entry ID: the ID of the entry to get. A record identifier, never the title, which is the mistake that returns a 404 most often.

Use cases

an approval message in chat carries a record id, and the workflow fetches the full text before sending it for review.

Get many entries

entry.getAll

What you see in n8n

Notes & use cases

Lists the records of a collection type. This is the read operation that feeds exports, digests and syncs.

Key parameters

Content Type: the collection type to list.
Return All: on, n8n walks the API pages until every entry is back; off, Limit caps how many records come out.
Publication State: live keeps published records only, preview also brings back drafts.
Sort Fields: field names, ascending by default, with a direction after a colon as in name:asc.
Where (JSON): a JSON query that filters the records before they leave Strapi.

Use cases

a Monday digest of everything published last week, sorted and filtered before it reaches your inbox.

Update an entry

entry.update

What you see in n8n

Notes & use cases

Writes new values on records that already exist, matched on a property you choose rather than on a position in a list.

Key parameters

Content Type: the content type to modify.
Update Key: the property that decides which rows in the database get updated, normally id.
Columns: the comma-separated properties to overwrite. Only what you list changes; everything else stays as it was.

Use cases

a price or a stock level changes in your back office and the matching product entry is refreshed on the site.

Need help

Need help automating Strapi with n8n?

A person reads every message.

FAQ

Strapi and n8n, the questions that come next

01Is the Strapi n8n integration free?

Yes, on the n8n side. The Strapi node ships with n8n, so there is nothing to install and nothing extra to pay, whether you run n8n Cloud or a self-hosted instance under the Community Edition and its Sustainable Use licence. The same workflow behaves the same way in both places, which means you can build on Cloud and move later without rewriting the node. What your Strapi project itself costs depends on how you host it, and that sits outside what the node does. The only real budget question left is where you want your content data to live.

02Which credentials does the Strapi node need?

Two methods are supported. The first is an API user account: an Email and a Password belonging to an end user, not to an admin, plus a role configured in the Users and Permissions Plugin with the permissions that match your workflow, create, find and findone, update or delete, on each collection type you touch. The second is an API token, created from an admin account under Global Settings. Both methods also ask for the URL of your Strapi server and the API Version, 3 or 4. You create the credential once in n8n and every Strapi node in every workflow can pick it from a dropdown.

03What are the limits of the Strapi node?

The node covers one resource, Entry, with 5 operations. Any resource other than Entry, and anything a plugin adds on top of the REST API, is not part of it. Reads also need attention: with Return All off, the node stops at Limit, so an export that looks short is usually a Limit left in place. For calls the node does not expose, the HTTP Request node reaches any endpoint of the Strapi REST API and reuses the same credential through predefined authentication, which keeps your token in one place.

04Can n8n react to a new Strapi entry in real time?

Not on its own. Strapi has no trigger node in n8n, so a workflow that involves it always starts somewhere else. Two patterns cover almost everything. A Schedule Trigger runs at a fixed interval and calls entry.getAll to see what changed since the last pass, which suits digests, exports and syncs. Or an n8n Webhook, a URL that another service calls, starts the workflow the moment that service has news, and Strapi is then written to rather than watched. The trigger of another tool in your chain works just as well as the entry point.

05n8n or Make for Strapi?

It depends on where your content sits and how you want to pay. Make is hosted only, with no self-hosting option, and bills per operation, so a workflow that lists a large collection type every hour becomes a volume question. n8n runs on Cloud or on your own server, which matters when the Strapi project is internal and the entries hold customer data you would rather keep on your infrastructure. Both give you a visual canvas. The practical test is simple: count the operations a busy day would generate, then decide whether hosting the automation yourself is worth the maintenance.

Choose between a user account and a token

Give the role its permissions

Fill the credential inside n8n

Need help automating Strapi with n8n?