- Home
- Resources
- Integrations
- Contentful
Contentful Make integrationAutomate Contentful with Make.
What if your content team stopped copying text into Contentful by hand? The Contentful Make integration gives you 29 modules, including one instant trigger, to create, publish and tidy entries and assets. This page shows how to connect your space and build a first scenario.
Verified Trustpilot reviews · AI, automation & growth agency
What does the Contentful Make integration actually do?
The Contentful Make integration links your Contentful space to Make, a no-code tool where you build a scenario: an automation made of modules, each module being one brick that watches, acts or searches. In Contentful, an entry is one piece of content (an article, a product sheet), built on a content type, the model that sets its fields. Make creates it, publishes it (draft goes live) or archives it for you.
Drafts that write themselves. A product team fills a form in another tool, and Create an Entry turns each answer into a Contentful entry. Publish an Entry can follow when no review is needed, or the entry can stay in draft for an editor.
A clean media library. A marketing team that stores visuals elsewhere can push them with Create an Asset, then use Search Assets and Archive/Unarchive an Asset to retire old files without deleting them.
Other tools that follow Contentful. Watch an Event fires when something happens in your space, so a scenario can post a message to your team chat or log the change in a spreadsheet.
Keep in mind what the Make documentation does not cover: it lists the modules without detailing each field, and it flags its own Contentful pages as AI-generated content to check against the vendor. For anything the list misses, Make an API Call reaches the rest of the Contentful API with the same connection.
Contentful also has a node on n8n: see the Contentful n8n integration and our n8n vs Make comparison. New to the editor? The Make training starts from scratch.
How do you connect Contentful to Make?
- 01
Generate a token in Contentful
In Contentful, open Settings, then CMA tokens, and click Create access token. Give it a name you will recognize later, set an expiration date if your team requires one, click Generate and copy the token shown in the window.
- 02
Add a Contentful module in Make
In your Make scenario, add any Contentful module and click Create a connection. A connection is your Contentful account linked to Make once, then reused by every Contentful module. The Connection name field is optional, but a clear name helps when you have several spaces.
- 03
Paste the token and save
Paste the token you copied from Contentful into the credentials Make asks for, or follow the instructions on screen, then save. From now on, Make can list the content types, entries and assets your token gives it access to.
Your first scenario: turn a form answer into a published entry
GoalWhen a form in another app receives an answer, Make creates a Contentful entry and publishes it.
- 01
Create the scenario
On the Scenarios page, create a new scenario and click the +. Pick the app that collects your answers (a form tool, for example) and choose its trigger, the module that starts the flow.
- 02
Add Create an Entry
Click the + on the right of the first module, search Contentful and pick Create an Entry. Connect your account with the CMA token, then choose where the entry goes among the options Make lists.
- 03
Map the form answers
Fill each field of the entry with data from the form module: click a field and pick the matching answer. Each answer arrives as a bundle, one item passed from one module to the next.
- 04
Add Publish an Entry
Add Publish an Entry after it and map the ID returned by Create an Entry. Leave this module out if an editor should review each draft before it goes live.
- 05
Test with Run once
Submit a test answer, then click Run once. Make runs the scenario one time and shows the bundles each module received, so you can check the new entry in Contentful.
- 06
Schedule and switch it on
Set the schedule on the first module (every 15 minutes by default, unless the form app is instant) and switch the scenario on. Each module run counts as one operation on your Make plan.
What can start a Contentful scenario?
1 module starts a scenario when something happens in Contentful. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Contentful as soon as it happens.
Watch an Event
Instant triggerIn Make“Triggers when a new event occurs.”
Watch an Event starts your scenario the moment something happens in your Contentful space, so the rest of your tools learn about a change without anyone checking by hand. It is the only trigger of the app, which makes it the natural entry point for any flow that begins in Contentful.
What else can Make do in Contentful?
Contentful gives you 28 modules. For each one: what it does for you, when to reach for it, and what to watch out for.
Modules index
- Activate a Content Type
- Add a Field to a Content Type
- Archive/Unarchive an Asset
- Archive/Unarchive an Entry
- Create a Content Type
- Create an Asset
- Create an Entry
- Deactivate a Content Type
- Delete a Content Type
- Delete a Field from a Content Type
- Delete an Asset
- Delete an Entry
- Get a Content Type
- Get an Asset
- Get an Entry
- Get an Entry with Replacement
- Make an API Call
- Publish an Asset
- Publish an Entry
- Unpublish an Asset
- Unpublish an Entry
- Update a Content Type
- Update a Field of a Content Type
- Update an Asset
- Update an Entry
- Search Assets
- Search Content Types
- Search Entries
Activate a Content Type
ActionIn Make“Activates a content type by its ID. Use this module to apply new changes.”
Activating a content type makes your latest edits to its structure count, so new entries follow the updated model. Without this step, changes to a content type stay pending.
Add a Field to a Content Type
ActionIn Make“Adds a new field to a specific content type.”
This module extends an existing content model with a new field, for instance a slot for a subtitle your editors keep asking for. You change the structure from Make instead of the Contentful settings.
Archive/Unarchive an Asset
ActionIn Make“Archives/Unarchives an unpublished asset.”
Archiving hides a file from daily work while keeping it recoverable, and the same module brings it back. A softer option than deletion for a media library that grows fast.
Archive/Unarchive an Entry
ActionIn Make“Archives/Unarchives an unpublished entry.”
Here the target is an entry: an old article or an expired offer moves to the archive, out of your editors' way, and can return later with the same module.
Create a Content Type
ActionIn Make“Creates a new content type.”
Create a Content Type builds a brand new model, the template that defines which fields an entry has. Handy when you replicate the same structure across spaces or projects.
Create an Asset
ActionIn Make“Creates a new asset.”
Media coming from another tool lands in Contentful as an asset, ready to be attached to entries. No more downloading a file just to upload it again.
Create an Entry
ActionIn Make“Creates a new entry.”
This module writes a new piece of content, filled with data from the previous modules. Product sheets, event pages or FAQ items can start life outside Contentful.
Deactivate a Content Type
ActionIn Make“Changes a content type status to "draft".”
Deactivating sends a content type back to draft status. It is the step that prepares a model for removal or for deeper rework.
Delete a Content Type
ActionIn Make“Permanently removes a deactivated content type.”
This one removes a content model for good. Use it to clean up test types or structures from a project that is over.
Delete a Field from a Content Type
ActionIn Make“Removes a field from a specific content type.”
A field nobody fills anymore can leave the model through this module, which keeps the editing screen short for your team.
Delete an Asset
ActionIn Make“Permanently removes an unpublished asset.”
Delete an Asset removes a file from Contentful for good, which frees the library from duplicates and abandoned uploads.
Delete an Entry
ActionIn Make“Permanently removes a specific entry.”
With this module, an entry disappears permanently from your space. It fits cleanup flows where drafts pile up and nobody will ever publish them.
Get a Content Type
ActionIn Make“Returns attributes of a specific content type.”
Reading a content type gives your scenario its attributes from its ID. Other modules can then use that information.
Get an Asset
ActionIn Make“Returns attributes of a specific asset.”
Get an Asset fetches the details of one file you already know the ID of, so later modules can reuse what Contentful returns about it.
Get an Entry
ActionIn Make“Returns attributes of a specific entry.”
This module reads one entry in full from its ID. It usually sits right after the trigger, to turn an event into content your other apps can use.
Get an Entry with Replacement
ActionIn Make“Allows to replace text fields with new values by using specific tags ( e.g: {{!notfound:name}}, {{!notfound:email}} ). Returns new values as output.”
This variant reads an entry and swaps tags placed in its text fields for values you provide, such as {{!notfound:name}}. Your Contentful text becomes a reusable template.
Make an API Call
ActionIn Make“Performs an arbitrary authorized API call.”
When none of the other Contentful modules covers your need, this one calls any endpoint of the Contentful API with the connection you already set up.
Publish an Asset
ActionIn Make“Changes asset status to "published".”
Publishing makes a file live, available to the site or app that reads your Contentful space. It is the step that follows Create an Asset or Update an Asset.
Publish an Entry
ActionIn Make“Changes entry status to "published".”
Your entry goes live through this module, in the same flow that created or updated it. Draft becomes published without a manual click.
Unpublish an Asset
ActionIn Make“Puts an asset back into "draft" state.”
An asset returns to draft here: it stops being served but stays in the library, editable and ready to publish again.
Unpublish an Entry
ActionIn Make“Puts an entry back into "draft" state.”
Taking an entry offline without losing it: the content goes back to draft and your editors can fix it quietly.
Update a Content Type
ActionIn Make“Updates a specific content type by its ID.”
Update a Content Type edits an existing model from its ID, without rebuilding it from scratch.
Update a Field of a Content Type
ActionIn Make“Updates a field inside a specific content type.”
Targeting one field, this module changes it inside a content type while the rest of the model stays untouched.
Update an Asset
ActionIn Make“Updates an asset by its ID.”
An existing file gets new details through this module, from its ID, while entries that use it keep pointing to the same asset.
Update an Entry
ActionIn Make“Updates a specific entry by its ID.”
Update an Entry rewrites an entry already in Contentful, found by its ID, with fresh data from another tool. Prices, dates or descriptions stay in sync.
Search Assets
SearchIn Make“Searches for assets.”
Searching assets returns every file that matches, each one as its own bundle, so the next modules process them one by one.
Search Content Types
SearchIn Make“Searches for content types.”
This search lists the content models of your space, which is how a scenario finds the ID every content type module needs.
Search Entries
SearchIn Make“Searches for entries.”
Search Entries finds the content that matches your criteria and hands back each entry as a bundle, ready for an update, an export or a report.
Need help automating Contentful with Make?
A person reads every message.