A Contentful MCP that writes to the CMS, not just reads it
Connect one Content Management API token and spaces, environments, content types, entries, assets, locales, tags, webhooks, scheduled publishing and bulk actions become workflow steps. An agent can read an entry, patch one field with the version it just read, and publish it, while the run history sits next to your tasks and databases instead of in a terminal.
What the Contentful MCP connector does
The Contentful connector for Mattering Automations is 52 nodes on the Content Management API: spaces and environments, content types with activate and deactivate, editor interfaces, entries across their whole lifecycle (create, create or update, JSON Patch, publish, unpublish, archive, unarchive, delete), assets including the process and publish steps, locales, tags, space level webhooks with their recent call log, roles, Delivery API keys, scheduled actions, and bulk publish, unpublish and validate. One management token authenticates all of it, and the credential also carries the data residency that selects the API host.
Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and any MCP-capable assistant can use them, alongside Matter, the AI assistant built into the platform. An agent can list a space's content types, read an entry with its current version, change one value with JSON Patch, and publish the result, without anyone opening the Contentful web app.
Three Contentful mechanics shape every write, and the nodes state each one rather than letting you discover it in production. Writing to an existing resource sends its current sys.version in a header, and a stale version is refused with a 409, so the read before the write is part of the design. Entry and asset fields are locale keyed, maps of field id to a map of locale code to value, so the shape of a field value depends on how many locales the environment has. And the API does not merge: a create or update call replaces the object whole, so anything left out is lost. Contentful: Patch Entry exists for exactly that reason, changing single values through JSON Patch instead of resending the entry.
The scope and the safety modeling are stated plainly. Of the 52 nodes, 20 read and 32 act, and 7 carry a destructive flag: the environment, content type, entry, asset, locale, tag and webhook deletes. The Content Management API documents no trash and no restore for those, so the pattern the node descriptions push is read first, then delete behind a gate. Deliberately outside this connector: the Content Delivery API (a different token, a different host, and a different response shape, and the management API already reads published content with the same token), raw binary uploads (assets are created from a publicly reachable file URL instead), and releases, which this build leaves out on its own reading of the create-a-release payload: it takes more than one shape, and no single node form serves them all honestly.
One connection, three surfaces
- Visual automations. Drag Contentful nodes onto the canvas and wire them to triggers, conditions, and other apps.
- AI agents, yours or ours. These nodes speak MCP, the open protocol, so Claude, ChatGPT, and any MCP-capable assistant can use them, and Matter, the agent built into the platform, uses them natively.
- The whole platform. Combine with native tasks, projects, and other connectors, no middleware in between.
Every Contentful node, ready to drop on the canvas
52 nodes, generated from the connector itself so this list always matches what ships. Expand a category to browse.
Read and query nodes 20
Contentful: Get Asset
Fetch one asset with all of its locales, its file details and its current sys.version. A processed asset carries fields.file.<locale>.url; an unprocessed one still carries only the upload URL you gave it.
Contentful: Get Bulk Action
Read the status of a bulk action: created, inProgress, succeeded or failed, with an error object when it failed. Bulk actions run asynchronously, so this is how a workflow waits for one. Records are kept for 7 days.
Contentful: Get Content Type
Fetch one content type with its complete field list, validations and current sys.version. The read to do before Create or Update Content Type, because that write replaces the field list whole.
Contentful: Get Editor Interface
Fetch a content type's editor interface: which widget renders each field, the sidebar layout, and the current sys.version. The read to do before Contentful: Update Editor Interface, which requires that version.
Contentful: Get Entry
Fetch one entry with all of its locales and its current sys.version. The read to do before any write, since updates replace fields whole and need the version. Empty fields are omitted from the response, so a missing key means no value rather than an error.
Contentful: Get Environment
Fetch one environment, including its creation state. A freshly created environment moves through queued and inProgress before it reaches ready, so poll this node after Create Environment before writing content into it.
Contentful: Get Space
Fetch one space with its name, organization and current sys.version. Ask for the space's license metadata by setting include to sys.license.
Contentful: Get Webhook Call Details
Fetch one webhook call in full: the exact request Contentful sent (URL, method, headers, body) and the response it received. The overview tells you a call failed; this tells you why.
Contentful: List Assets
List an environment's assets (images, video, documents), drafts included, with every locale. Each asset's title, description and file live under locale keyed fields, and fields.file.<locale>.url carries the CDN URL once the asset has been processed.
Contentful: List Content Types
List an environment's content types (the models entries follow), each with its full field schema, display field and current sys.version. This is where entry-shaped automations start: the content type id is what Create Entry needs.
Contentful: List Delivery API Keys
List a space's Delivery API keys with the environments each can read and a link to its paired Preview key. accessToken in the response IS the read-only delivery token, so treat this node's output as sensitive.
Contentful: List Entries
List an environment's entries, drafts included, with every locale (this is the management view, not the delivery view). Filter by content type, by full text, or with Contentful's field[operator]=value syntax through the additional query parameters, for example sys.updatedAt[gte] to fetch what changed since a date.
Contentful: List Environments
List a space's environments. Every space has master; sandbox environments are point-in-time copies of it used for QA, staging or CI. The id is the name you use in every other node.
Contentful: List Locales
List an environment's locales. Exactly one has default set to true; that is the locale the Delivery API serves when a request names none. The code is the key inside every entry and asset fields object, so this node is how you learn what those keys are.
Contentful: List Roles
List a space's roles with their permissions and policies, which is what an access audit needs: each policy says which actions are allowed on which content.
Contentful: List Scheduled Actions
List the publishes and unpublishes waiting on a schedule, for one environment. Cursor paginated: the response carries a pages object rather than a total. Filter to one entry or asset, or to a status, to see what is queued for it.
Contentful: List Spaces
List the spaces the management token can access, with their ids, names and organization. Every other Contentful node needs a space id from here. Also the credential health check: a bad or delivery-only token returns 401.
Contentful: List Tags
List an environment's tags, the labels used to group entries and assets. Tags are scoped to one environment. sys.visibility says whether a tag is private (management only) or public (visible through the Delivery API too).
Contentful: List Webhook Calls
List recent attempts for one webhook, each with the event type, response status code, timings and any errors. This is the first stop when a downstream build stopped triggering: it tells you whether Contentful called at all and what it got back.
Contentful: List Webhooks
List a space's webhooks with their target URL, topics, filters and headers. Webhooks are space level rather than environment level: a webhook with no environment filter fires for every environment, and one with no filters property at all fires only for master.
Action nodes 32
Contentful: Archive Entry
Archive an entry, hiding it from the app's normal content views without deleting it. An entry can only be archived while it is unpublished, so run Contentful: Unpublish Entry first. Reversible with Contentful: Unarchive Entry.
Contentful: Bulk Publish
Publish up to 200 entries and assets in one asynchronous action. It returns immediately with a bulk action whose sys.status starts at created: poll Contentful: Get Bulk Action with data.sys.id to learn whether it succeeded. A space can have 5 active bulk actions at once. Reversible with Contentful: Bulk Unpublish.
Contentful: Bulk Unpublish
Unpublish up to 200 entries and assets in one asynchronous action, returning them all to draft. Poll Contentful: Get Bulk Action with data.sys.id for the outcome. Nothing is deleted. Reversible with Contentful: Bulk Publish.
Contentful: Bulk Validate
Check whether a batch of entries and assets would pass validation, WITHOUT publishing anything. Run this before Contentful: Bulk Publish to find the entries that would fail. It changes no content, but it does create a bulk action record, so poll Contentful: Get Bulk Action with data.sys.id for the result.
Contentful: Cancel Scheduled Action
Cancel a pending scheduled action so it never runs. Only actions still in scheduled status can be cancelled; one that already ran cannot be undone from here. Nothing is deleted from the content itself, so this is reversible by scheduling again.
Contentful: Create Entry
Create an entry and let Contentful generate its id. The content type travels in a header, and the field values are locale keyed. The content type must be activated first. New entries are drafts: run Contentful: Publish Entry to make them visible to the Delivery API. Reversible with Contentful: Delete Entry.
Contentful: Create Environment
Create an environment with an id you choose, as a copy of master or of the source environment you name. Cloning is a heavy operation whose duration scales with how much content the source holds, so check Contentful: Get Environment until the state is ready before using it. Reversible with Contentful: Delete Environment.
Contentful: Create Locale
Add a locale to an environment, which adds a new key to every entry and asset fields object. Two locales cannot share a code. Reversible with Contentful: Delete Locale, but note that deleting takes the translated content with it.
Contentful: Create Scheduled Action
Schedule an entry or asset to publish or unpublish at a future time, which is how an embargo or a timed campaign is built. The time must fall between now and five years ahead. An environment can hold at most 500 scheduled actions in scheduled status, with a separate limit of 200 executing in any single minute. Reversible with Contentful: Cancel Scheduled Action while it is still pending.
Contentful: Create or Update Asset
Create an asset with an id you choose, or update an existing one. Point the file at a publicly reachable URL and Contentful fetches it during processing. Creating an asset takes three calls: this one, then Contentful: Process Asset, then Contentful: Publish Asset. fields is REPLACED whole, so read the asset first when updating.
Contentful: Create or Update Content Type
Create a content type with an id you choose, or update an existing one. IMPORTANT: fields is REPLACED whole, not merged, so read the current type with Contentful: Get Content Type, edit its fields array, and send it all back. A new content type is a draft until Contentful: Publish Content Type activates it.
Contentful: Create or Update Entry
Create an entry with an id you choose, or update an existing one. IMPORTANT: fields is REPLACED whole. Read the entry with Contentful: Get Entry, change the values you want, and send the entire fields object back, or every value you left out is lost. Send the content type when creating and the version when updating.
Contentful: Create or Update Tag
Create a tag with an id you choose, or rename an existing one. Name and id must both be unique in the environment. The id and the visibility cannot be changed after creation, so choose both deliberately. Only space admins and users with tag permissions can run this.
Contentful: Create or Update Webhook
Create a webhook with an id you choose, or update an existing one. Topics are what fires it, for example Entry.publish. Every list you send replaces its counterpart whole, so read the current definition from Contentful: List Webhooks before editing. Reversible with Contentful: Delete Webhook.
Contentful: Delete Asset
DESTRUCTIVE: delete an asset and every file it ever referenced on the CDN. There is no restore. Removal from the CDN takes between 24 and 48 hours, and only once the asset is deleted or archived in EVERY environment, so a file that keeps serving is usually a copy still live elsewhere rather than a delete that failed. Capture the asset with Contentful: Get Asset first.
Contentful: Delete Content Type
DESTRUCTIVE: delete a content type permanently. It must be deactivated first with Contentful: Unpublish Content Type, and it cannot be deleted while entries still use it. Capture the definition with Contentful: Get Content Type before running this.
Contentful: Delete Entry
DESTRUCTIVE: delete an entry permanently. The CMA documents no trash and no restore, and other entries linking to this one are left pointing at nothing. Capture it with Contentful: Get Entry first, and prefer Contentful: Archive Entry when you only want it out of the way.
Contentful: Delete Environment
DESTRUCTIVE: delete a sandbox environment and everything inside it (entries, assets, content types, locales). The master environment cannot be deleted. There is no trash and no restore, so export anything you might want first.
Contentful: Delete Locale
DESTRUCTIVE: delete a locale AND all content translated into it, across every entry and asset in the environment. Contentful states this cannot be undone, and recreating the same locale does not bring the content back. A locale used as another locale's fallback cannot be deleted.
Contentful: Delete Tag
DESTRUCTIVE: delete a tag and strip it from every entry and asset that carried it. The grouping is gone and recreating the tag does not reattach it, so anything that filtered on this tag stops matching.
Contentful: Delete Webhook
DESTRUCTIVE: delete a webhook definition and its call history. Anything downstream that depended on the notification stops silently. To stop a webhook temporarily instead, set active to false with Contentful: Create or Update Webhook.
Contentful: Patch Entry
Change individual entry values with JSON Patch, without resending the whole entry. This is the surgical alternative to Create or Update Entry, and the safer one when several automations touch the same entry. The version is REQUIRED. Note that a patch cannot address a field that has never been set: for those, add the whole locale keyed sub-object instead.
Contentful: Process Asset
Process an asset's file for one locale: Contentful fetches the upload URL into its own storage. This is the required middle step between creating an asset and publishing it, and it runs per locale. It returns 204 with no body and may finish after the response, so read the asset back and wait for fields.file.<locale>.url to appear before publishing.
Contentful: Publish Asset
Publish an asset so it is served by the Delivery API and the asset CDN. Images become available from the image CDN with the Images API resize and crop parameters. The file must have been processed first. Reversible with Contentful: Unpublish Asset.
Contentful: Publish Content Type
Activate a content type, which is what makes it usable for entries and visible to the Delivery API. Contentful calls this activating; it is the same PUT on /published that publishes an entry. Validations take effect for entries published after this. Reversible with Contentful: Unpublish Content Type.
Contentful: Publish Entry
Publish an entry, making it available through the Delivery API. Publishing is a separate call from saving: a draft stays invisible until this runs. Reversible with Contentful: Unpublish Entry.
Contentful: Unarchive Entry
Bring an archived entry back to draft, where editors can see and publish it again. Reversible with Contentful: Archive Entry.
Contentful: Unpublish Asset
Unpublish an asset: it goes back to draft and stops being delivered. Entries that reference its CDN URL will show a missing file until it is published again. Reversible with Contentful: Publish Asset.
Contentful: Unpublish Content Type
Deactivate a content type: it stops being delivered and no new entries can use it, while the definition itself stays. This is the required step before Contentful: Delete Content Type. Reversible with Contentful: Publish Content Type.
Contentful: Unpublish Entry
Unpublish an entry: it disappears from the Delivery API and returns to draft. Nothing is deleted, the content stays editable. Reversible with Contentful: Publish Entry.
Contentful: Update Editor Interface
Update how a content type is presented to editors: the widget per field, the sidebar, and the entry editor. The version field is REQUIRED here. Each block you send replaces its counterpart whole, so read the current interface first with Contentful: Get Editor Interface.
Contentful: Update Locale
Update a locale. The version field is REQUIRED. Changing the code changes the keys in every future API response and will break clients that expect the old one, and it is refused outright while another locale uses this one as its fallback. The default flag cannot be changed.
Connecting Contentful takes one credential
Contentful authenticates management requests with a Content Management API token, sent as a bearer token on every request. Personal access tokens are created in the Contentful web app: open the space, click Settings, select CMA tokens from the drop-down, then click Create personal access token; an OAuth or app token works too. The tokens most teams already have will not work here: Delivery and Preview tokens live on the Settings then API keys screen, they are read-only credentials for different hosts, and they return 401 against the management API. The credential also carries a data residency setting, because accounts on EU data residency talk to a different API host, and an optional default space id so a single-space team does not retype the same id on every node.
In Contentful, open the space, click Settings, select CMA tokens from the drop-down, then click Create personal access token. Copy it when it is shown.
In Mattering Automations, open Connectors, click Add Connector, choose Contentful, and create a credential with the token. Set the data residency to match the account, and add a default space id if you work in one space.
Click Test Connection. Mattering calls the space list endpoint and reports how many spaces the token can see. A 401 or 403 here means one of two things: the token is a Delivery or Preview token rather than a management token, or the data residency does not match the account.
All 52 Contentful nodes appear in the canvas palette. Run Contentful: List Spaces first, then Contentful: List Environments and Contentful: List Content Types, because the space id, environment id and content type id are what almost every other node asks for.
Common uses for the Contentful MCP
An AI agent that edits entries without wiping them
This is the workflow the connector is shaped around. Contentful: Get Entry returns the entry with every locale and its current sys.version, and then there are two ways to write. Contentful: Patch Entry changes individual values with JSON Patch, which is the safe default when several automations touch the same entry, and Contentful: Create or Update Entry sends the whole fields object back when the change is broad. The version travels with the write, so a conflicting edit is refused rather than silently overwritten. One documented limit sits on the patch node: a patch cannot address a field that has never been set on the entry, so a first-time value needs the whole locale keyed sub-object added instead.
Publish pipelines that separate saving from going live
In Contentful, saving and publishing are different calls, which is exactly what makes a review step possible. A workflow can create a draft with Contentful: Create Entry, hold it for a human approval task, and only then run Contentful: Publish Entry, with Contentful: Unpublish Entry as the one-node rollback. Contentful: Archive Entry moves finished content out of the editors' way without deleting it, and Contentful: Unarchive Entry brings it back. Content types follow the same pair through Contentful: Publish Content Type and Contentful: Unpublish Content Type, which Contentful calls activating and deactivating.
Assets built from a URL, in the three steps the API requires
Creating an asset is not one call. Contentful: Create or Update Asset points the file at a publicly reachable URL, Contentful: Process Asset makes Contentful fetch it into its own storage for one locale, and Contentful: Publish Asset puts it on the delivery CDN. Processing answers with no body, and that response is not a promise the file is ready, so the reliable pattern is to read the asset back with Contentful: Get Asset and wait for the file URL to appear before publishing. This is the reason the connector needs no binary upload node: the automation already has a URL for the file it wants to add.
Bulk publishing with a validation pass first
Contentful: Bulk Validate checks whether a batch of entries and assets would pass validation without publishing anything, which turns a risky release into a report. Contentful: Bulk Publish then publishes up to 200 items in one asynchronous action, and Contentful: Bulk Unpublish reverses it. All three return immediately with a bulk action record rather than a result, so the workflow polls Contentful: Get Bulk Action until the status settles. Contentful documents a limit of 5 active bulk actions per space and 200 items per action, and keeps the records for 7 days.
Environments as disposable content branches
Contentful: Create Environment clones master, or another environment you name, into a sandbox you can rebuild a content model in. Cloning is heavy and its duration scales with how much content the source holds, so the workflow polls Contentful: Get Environment until the state is ready before writing into it. From there, Contentful: Create or Update Content Type and Contentful: Update Editor Interface shape the model, Contentful: List Environments keeps an inventory, and the destructive-flagged Contentful: Delete Environment cleans up when the branch merges. Master cannot be deleted, which removes the worst version of that mistake.
Scheduled campaigns and webhook health, watched from the same canvas
Contentful: Create Scheduled Action queues an entry or asset to publish or unpublish at a future time, which is how an embargo or a timed campaign is built, and Contentful: List Scheduled Actions and Contentful: Cancel Scheduled Action manage the queue (Contentful documents a limit of 500 scheduled actions in scheduled status per environment, a separate limit of 200 scheduled actions executing in any single minute, and a scheduled time that has to fall between now and up to five years ahead). On the delivery side, Contentful: List Webhook Calls shows recent attempts with their status codes and timings, and Contentful: Get Webhook Call Details shows the exact request and response for one of them, so a downstream build that stopped triggering gets diagnosed from a workflow rather than from a support ticket.
Example: An approved article ships: image first, then the entry, then publish
Built on the Automations canvas in a few minutes, or described in plain language to Matter and built for you.
Trigger: a Mattering Productivity task moves to Approved, carrying the article body, the hero image URL and the content type to use.
Contentful: Create or Update Asset creates the image asset from the public file URL, with the title and file locale keyed.
Contentful: Process Asset fetches the file into Contentful storage, then Contentful: Get Asset reads it back until the processed file URL is present.
Contentful: Publish Asset puts the image on the delivery CDN so the entry can reference it.
Contentful: Create Entry creates the article draft against the content type, with the asset linked and the fields keyed by locale.
Contentful: Publish Entry makes it live, and the workflow comments the entry id and the run link back on the task so the reviewer can see what shipped.
Contentful MCP questions, answered
What Contentful operations are supported?
52 nodes on the Content Management API: 20 query nodes and 32 action nodes. Spaces (list, get), environments (list, get, create as a clone, delete), content types (list, get, create or update, activate, deactivate, delete), editor interfaces (get, update), entries (list, get, create, create or update, JSON Patch, publish, unpublish, archive, unarchive, delete), assets (list, get, create or update, process, publish, unpublish, delete), locales, tags, space webhooks with their recent call log and full call details, roles for access audits, Delivery API keys, scheduled actions (list, create, cancel), and bulk publish, unpublish and validate with a status read. Deliberately not included: the Content Delivery API, raw binary uploads, releases, snapshots, and the organization and app administration surfaces.
Does this work with Claude, ChatGPT, or other AI assistants?
Yes. Mattering exposes these nodes over MCP, an open protocol for connecting AI assistants to tools, so any MCP-capable assistant, including Claude and ChatGPT, can connect to your workspace and use them. Matter, the assistant built into the platform, uses the same nodes natively.
Contentful ships its own MCP server. Why would I use this one?
Contentful does ship one, a hosted server at https://mcp.contentful.com/mcp and a local open source server run with npx @contentful/mcp-server, covering content types, entries, assets, spaces, environments, locales, tags and AI Actions. The honest difference is where the tools run. If all you need is an assistant talking to one Contentful space, Contentful's own server is the shorter path and worth using. These nodes exist because they are steps in a workflow canvas, so the same call sits beside a Mattering Productivity task, a database write, an approval gate or any other connector, fires on a schedule or a trigger rather than only when someone is chatting, and leaves its run history next to the rest of your automations.
Which Contentful token does this need, and will my delivery token work?
It needs a Content Management API token, created in the Contentful web app by opening the space, clicking Settings, selecting CMA tokens from the drop-down and then Create personal access token, or issued through OAuth or an app. The Settings then API keys screen is a different place and the wrong one here: it holds Delivery and Preview tokens, which are read-only credentials for different hosts, and they return 401 against the management API. This trips people up because delivery tokens are the ones most teams already have to hand, so the connection test names the distinction in its failure message. There is a second cause of the same 401 or 403: accounts on EU data residency use a different API host, and the credential carries a residency setting that has to match the account.
What are Contentful's API rate limits?
Contentful's Content Management API documents a default of 7 requests per second, with higher limits available on some plans; this page will not put a number on the per-plan figures. Every response carries the current second limit, the remaining allowance, and a reset value, and a 429 sets that reset to the number of seconds to wait. Nodes report a rate limit error on their output rather than retrying silently, so a workflow can wait and continue rather than failing the whole run.
Can an automation update one field without losing the rest of the entry?
Yes, with Contentful: Patch Entry, and that node exists because the alternative genuinely does lose data. The management API does not merge: a create or update call replaces the object whole, so an update that sends only the changed field wipes every field it left out. The safe patterns are therefore two. Either patch, which sends JSON Patch operations and touches only what you name, or read with Contentful: Get Entry, edit the returned fields object, and send all of it back with the version. One patch limitation is documented on the node: a patch cannot address a field that has never been set, so a first value has to be added as the whole locale keyed sub-object.
What is the version header, and why does a write fail with a 409?
Contentful uses optimistic locking. Writing to an existing resource sends its current sys.version, and if the resource changed since you read it, the write is refused with a 409 rather than overwriting someone else's edit. In practice that means reading the resource in the step before the write and passing the version through, which is exactly what the node descriptions tell you to do. The version is required on the pure update nodes (Patch Entry, Update Locale, Update Editor Interface) and optional on the create or update nodes, because the same endpoint also creates resources that have no version yet. On publish, unpublish, archive and delete it is optional, and sending it anyway is the habit that stops a workflow from publishing a draft someone changed after it was read.
Why do entry and asset ids have no dropdown picker?
Because there is no honest label to show in one. Space, environment, content type, locale, tag, webhook and scheduled action fields all offer pickers that list real names. An entry does not: its human readable title lives inside locale keyed fields, under a display field that differs for every content type, so no single path can address it and a picker would list raw ids twice over, which is worse than a text box. Assets have the same problem in a different form, since an asset title is keyed by locale code. So those ids are free text, and the field descriptions point at Contentful: List Entries and Contentful: List Assets, which is where a workflow gets the ids to feed them.
What happens if an automation deletes something in Contentful?
It is gone. Seven nodes are flagged destructive (environment, content type, entry, asset, locale, tag and webhook deletes) and the management API documents no trash and no restore for any of them. Three deserve extra caution. Deleting a locale also deletes every translation into it across the whole environment, and recreating the locale does not bring the content back; Contentful refuses the delete outright in two cases, because a space's default locale cannot be deleted and neither can a locale that another locale uses as its fallback. Deleting an asset removes the files it referenced, and Contentful documents that removal from the CDN takes between 24 and 48 hours, and only once the asset has been deleted or archived in every environment, so a file that keeps serving is usually a copy still live in another environment rather than a delete that failed. Deleting an environment takes everything inside it. The safe pattern is the one the nodes describe: read the object first so the run holds a copy, prefer Contentful: Archive Entry when you only want something out of the way, and put deletes behind a condition or an approval step rather than a bare trigger.
Can it publish only certain locales of an entry?
The publish nodes carry an optional field for it, and Contentful documents locale based publishing as available only on specific pricing plans, pointing you at your Contentful sales contact to confirm which ones, so whether it works depends on your plan rather than on the connector. Left blank, which is the default, Contentful: Publish Entry and Contentful: Publish Asset publish the whole entry or asset. Everything else about locales is plan neutral: Contentful: List Locales tells a workflow which locale codes are in play, and those codes are the keys inside every fields object the entry and asset nodes read and write.
Put Contentful to work inside your workspace
Connect once, then use every node in visual automations and AI agent workflows across the Mattering platform.
All product names, logos, and brands are property of their respective owners and are used for identification purposes only. Use of these names, logos, and brands does not imply endorsement or affiliation. Contentful is a product of its respective owner; Mattering is an independent platform.