Resources · Make integration

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 you can automate

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.

Connect

How do you connect Contentful to Make?

  1. 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.

  2. 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.

  3. 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.

First scenario

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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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.

Triggers

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.

Contentful1Watch an Event

Watch an Event

Instant trigger

In MakeTriggers 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.

How it fires
instant: Contentful calls Make through a webhook as soon as the event happens, which is why the module carries the lightning badge.
When to use it
when a change in your space should notify your team chat or add a line to a tracking sheet.
Watch out
when you add it, click Create a webhook before Create a connection, or Contentful has no address to notify.
Modules

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.

Contentful1

Activate a Content Type

Action

In MakeActivates 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.

When to use it
right after a scenario adds, updates or deletes a field, as the final step that applies the new structure.
Watch out
the module works from the content type ID, so fetch it first with Search Content Types if you only know its name.
Contentful2

Add a Field to a Content Type

Action

In MakeAdds 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.

When to use it
when several spaces must receive the same new field and doing it by hand invites mistakes.
Watch out
follow it with Activate a Content Type, otherwise the new field is not applied.
Contentful3

Archive/Unarchive an Asset

Action

In MakeArchives/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.

When to use it
when a campaign ends and its visuals should leave the library view without being lost.
Watch out
it only accepts unpublished assets, so run Unpublish an Asset first on anything live.
Contentful4

Archive/Unarchive an Entry

Action

In MakeArchives/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.

When to use it
when a promotion ends in your e-commerce tool and its landing text should disappear from the working list.
Watch out
an entry must be unpublished before it can be archived; chain Unpublish an Entry right before.
Contentful5

Create a Content Type

Action

In MakeCreates 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.

When to use it
when a new project kicks off in your project tool and needs its own content model in Contentful.
Watch out
a fresh content type still needs its fields, then an activation, before editors can fill it.
Contentful6

Create an Asset

Action

In MakeCreates 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.

When to use it
when a designer drops a final visual in a shared drive and the web team needs it in Contentful.
Watch out
a new asset is not live yet; add Publish an Asset when it should appear on the site.
Contentful7

Create an Entry

Action

In MakeCreates 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.

When to use it
when a form answer, a spreadsheet row or a CRM record should become a draft for your editors.
Watch out
the entry stays in draft; Publish an Entry is a separate step, which is useful if someone must review first.
Contentful8

Deactivate a Content Type

Action

In MakeChanges 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.

When to use it
when a content model is retired, for instance an old event format your team no longer uses.
Watch out
Delete a Content Type only accepts a deactivated type, so this module almost always comes just before it.
Contentful9

Delete a Content Type

Action

In MakePermanently 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.

When to use it
when a sandbox space collects test models that nobody needs anymore.
Watch out
the removal is permanent and only works on a type that was deactivated first, so place Deactivate a Content Type before it and test with Run once on a copy.
Contentful10

Delete a Field from a Content Type

Action

In MakeRemoves 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.

When to use it
when the same obsolete field must go from a content type in several spaces at once.
Watch out
think about the entries that use that field, and the change only applies after Activate a Content Type; check the entries before you run it.
Contentful11

Delete an Asset

Action

In MakePermanently removes an unpublished asset.

Delete an Asset removes a file from Contentful for good, which frees the library from duplicates and abandoned uploads.

When to use it
when a rights period ends and a photo must no longer be stored anywhere.
Watch out
there is no undo, and the asset has to be unpublished first; if you only want it out of sight, Archive/Unarchive an Asset is the safer choice.
Contentful12

Delete an Entry

Action

In MakePermanently 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.

When to use it
when a deal is marked lost in your CRM and the draft case study written for it has no reason to exist.
Watch out
nothing brings the entry back; archive instead if there is any doubt.
Contentful13

Get a Content Type

Action

In MakeReturns 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.

When to use it
before adding or updating a field, to check what the model already contains and avoid duplicates.
Watch out
it needs the ID; when you only know the name, Search Content Types finds it.
Contentful14

Get an Asset

Action

In MakeReturns 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.

When to use it
when an entry points to an image and your newsletter tool needs that image to build an email.
Watch out
it returns one asset only; to find files by other criteria, Search Assets is the right tool.
Contentful15

Get an Entry

Action

In MakeReturns 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.

When to use it
when Watch an Event fires and the next module needs the complete text of the entry concerned.
Watch out
no ID, no result; map it from the previous module rather than typing it.
Contentful16

Get an Entry with Replacement

Action

In MakeAllows 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.

When to use it
when one entry holds a welcome message and each new customer should receive it with their own name.
Watch out
the new values come back as the module's output; the entry itself is not changed in Contentful.
Contentful17

Make an API Call

Action

In MakePerforms 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.

When to use it
for an operation the list does not offer, once you have found the right request in the Contentful developer docs.
Watch out
you write the request yourself, so test it with Run once and read the returned bundle before adding more modules.
Contentful18

Publish an Asset

Action

In MakeChanges 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.

When to use it
when an approved visual should go online without an editor opening Contentful to click the button.
Watch out
publish only what is final; pulling it back needs Unpublish an Asset.
Contentful19

Publish an Entry

Action

In MakeChanges 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.

When to use it
when a status changes to approved in your project tool and the matching article should go online.
Watch out
keep a human validation step before it if the content comes from outside sources.
Contentful20

Unpublish an Asset

Action

In MakePuts 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.

When to use it
when a legal team flags an image and it must go offline while the case is checked.
Watch out
archiving and deletion both require an unpublished asset, so this module often opens a cleanup flow.
Contentful21

Unpublish an Entry

Action

In MakePuts 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.

When to use it
when a product goes out of stock in your shop and its page should stop showing.
Watch out
every entry that should later be archived needs this step first, since archiving refuses published entries.
Contentful22

Update a Content Type

Action

In MakeUpdates a specific content type by its ID.

Update a Content Type edits an existing model from its ID, without rebuilding it from scratch.

When to use it
when several spaces share a model and a change must reach all of them the same way.
Watch out
the change waits for Activate a Content Type; for a single field, Update a Field of a Content Type is more precise.
Contentful23

Update a Field of a Content Type

Action

In MakeUpdates 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.

When to use it
when a field label or setting must evolve without touching the other fields your editors rely on.
Watch out
run Get a Content Type first to confirm the field exists, then activate the type to apply the edit.
Contentful24

Update an Asset

Action

In MakeUpdates 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.

When to use it
when a product photo is replaced in your digital asset tool and Contentful should follow.
Watch out
the module needs the asset ID; map it from Search Assets or the trigger rather than typing it.
Contentful25

Update an Entry

Action

In MakeUpdates 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.

When to use it
when an event date changes in your ticketing tool and the event page must show the new one.
Watch out
it needs the entry ID; map it from Search Entries or the previous module rather than typing it.
Contentful26

Search Assets

Search

In MakeSearches for assets.

Searching assets returns every file that matches, each one as its own bundle, so the next modules process them one by one.

When to use it
when you need to find files before an archive or delete step, without knowing their IDs.
Watch out
zero, one or many results can come back, and each bundle runs the next modules once, which counts as operations; narrow the search before you chain a delete.
Contentful27

Search Content Types

Search

In MakeSearches 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.

When to use it
at the start of a flow that edits models, when you know a type by name only.
Watch out
several types can match, so filter the results before passing them to an update or delete module.
Contentful28

Search Entries

Search

In MakeSearches 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.

When to use it
when you want to send every entry of a given type to a spreadsheet for a content audit.
Watch out
the search can return zero, one or many entries; test with Run once and read the bundles before you chain an update.
Need help

Need help automating Contentful with Make?

A person reads every message.

FAQ

Contentful and Make: common questions

01Is the Contentful Make integration free?
Yes, on the Make side: Contentful is a standard app, available from the Free plan. That plan allows 2 active scenarios, runs scheduled scenarios at most every 15 minutes, caps each run at 5 minutes and limits files to 5 MB. Paid plans go down to a 1 minute interval and remove the cap on active scenarios. Every module run counts as an operation on your plan. Your Contentful subscription is a separate matter: you need an active account there, and its pricing depends on Contentful, not on Make.
02What does it take to connect Contentful to Make?
You need an active Contentful account and an access token. In Contentful, go to Settings, then CMA tokens, click Create access token, name it, choose an expiration date if your team requires one, click Generate and copy the token. In Make, add any Contentful module, click Create a connection, optionally fill the Connection name, and paste the token. If the first module you add is the instant trigger Watch an Event, click Create a webhook first, then Create a connection.
03Does the Contentful trigger react in real time?
Yes. Watch an Event is an instant trigger: Contentful calls Make through a webhook as soon as the event happens, instead of Make checking on a schedule. It carries the lightning badge in the editor. This is the only Contentful trigger in Make. If your flow starts elsewhere, for example in a form tool or a spreadsheet, the scenario uses that app's trigger and its schedule, then Contentful modules take over as actions further down the chain.
04How do you handle a Contentful task that no module covers?
Use Make an API Call. This module calls any endpoint of the Contentful API with the connection you already have, so you are not limited to the listed actions and searches. You write the request yourself, based on the Contentful developer documentation, and test it with Run once. Also note that the Make documentation for Contentful is flagged as AI-generated, so check important details against Contentful's own documentation before building on them.
05Make or n8n for Contentful: which one fits?
It depends on the tool your team already works with. Contentful exists on both: in Make, you get 29 ready-made modules, including the instant Watch an Event trigger, and Make an API Call for the rest. n8n offers its own Contentful node, described on the Contentful n8n integration page. Compare the modules each one gives you against the tasks you need, try your first scenario on the one you plan to keep, and read the n8n vs Make comparison for the broader differences.