How to connect Contentful to OpenClaw
Connect Contentful to OpenClaw with ClawLink in one click — 106 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup.
ContentfulOAUTH2MCPHeadless CMS for structured content and digital experiences. Once connected, OpenClaw can read and act on Contentful from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Contentful access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Contentful setup: install one ClawHub skill, connect Contentful in the browser, and OpenClaw can call real Contentful actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Copy this prompt into OpenClaw, or open the Contentful skill on ClawHub.
Before installing anything, inspect the ClawHub skill metadata and setup requirements.
If the skill asks you to install a third-party package or CLI, verify its source, maintainer, and package contents before running the install command.
Install the skill "Contentful" (hith3sh/contentful-workspace) from ClawHub only after those checks pass.
Skill page: https://clawhub.ai/hith3sh/contentful-workspace
Keep the work scoped to this skill only.
After install, help me finish setup from verified skill metadata.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.Setup
It takes three steps to connect OpenClaw to Contentful.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Contentful
One-click OAuth in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Contentful?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect Contentful in the ClawLink dashboard — a one-click OAuth approval, no API keys.
Verify the connection by asking OpenClaw:
Use Contentful to activate content type and walk me through the result in plain English.
Using a different agent?
The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Contentful is connected in the dashboard, that agent calls the same 106 Contentful tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Contentful MCP for OpenClaw
Looking for a Contentful MCP server for OpenClaw? ClawLink connects Contentful to OpenClaw and exposes 106 Contentful tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Contentful integration works the same way.
What the OpenClaw Contentful integration can do
106 Contentful tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 106.
30 of 106 Contentful tools for OpenClaw
| Tool | What it does |
|---|---|
Activate content type contentful_activate_content_type | Activate (publish) a content type |
Archive asset contentful_archive_asset | Archive an asset |
Archive entry contentful_archive_entry | Archive an entry |
Archive release contentful_archive_release | Archive a release |
Get app definition contentful_get_app_definition | Retrieve details of a specific app definition |
Get asset contentful_get_asset | Retrieve a single asset by ID |
Get content types contentful_get_content_types | Retrieve all content types in an environment |
Get editor interface contentful_get_editor_interface | Retrieve editor interface configuration |
Get app bundle contentful_get_app_bundle | Retrieves details of a specific app bundle by its ID |
Get content type snapshot contentful_get_content_type_snapshot | Retrieve a snapshot of a content type by snapshot ID |
Get content type snapshots contentful_get_content_type_snapshots | Get all snapshots of a content type in Contentful |
Get entry comment contentful_get_entry_comment | Retrieve a specific comment from an entry in Contentful |
Get entry references contentful_get_entry_references | Retrieve references to a specific entry in Contentful |
Get entry snapshots contentful_get_entry_snapshots | Get all snapshots of an entry in Contentful |
Get environment contentful_get_environment | Retrieve details of a specific environment by its ID within a space |
Get organization contentful_get_organization | Retrieves details of a specific organization by its ID |
Get organization access grant contentful_get_organization_access_grant | Retrieves the access grant status for a specific organization |
Get organizations contentful_get_organizations | Get all organizations an account has access to in Contentful |
Get organizations AI providers contentful_get_organizations_ai_providers | Retrieves all AI providers configured for an organization in Contentful |
Get organizations app actions categories contentful_get_organizations_app_actions_categories | Retrieves app action categories for a Contentful organization |
Get organizations app def event subscription contentful_get_organizations_app_def_event_subscription | Retrieve details of an app event subscription by organization and app definition ID |
Get organizations app definitions contentful_get_organizations_app_definitions | Retrieves all app definitions for a specific organization |
Get organizations app definitions access grants contentful_get_organizations_app_definitions_access_grants | Get all app access grants for a specific app definition within an organization |
Get organizations app definitions actions contentful_get_organizations_app_definitions_actions | Get all actions of an app definition within an organization |
Get organizations app definitions actions2 contentful_get_organizations_app_definitions_actions2 | Read a specific app action from an app definition within an organization |
Get organizations app definitions app bundles contentful_get_organizations_app_definitions_app_bundles | Get all app bundles for a specific app definition within an organization |
Get organizations app definitions functions contentful_get_organizations_app_definitions_functions | Get all functions of an app definition within an organization |
Get organizations app definitions keys contentful_get_organizations_app_definitions_keys | Retrieve all app keys for a specific app definition in a Contentful organization |
Get organizations app definitions signing secret contentful_get_organizations_app_definitions_signing_secret | Retrieve the current app signing secret for an app definition |
Get organizations enablements contentful_get_organizations_enablements | Retrieves feature enablements for a specific organization in Contentful |
Try it: find the Contentful tool you need
Browse the 30 Contentful tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use Contentful to activate content type and walk me through the result in plain English.
Before using Contentful to archive asset, show me what will change and ask for confirmation.
Before using Contentful to archive entry, show me what will change and ask for confirmation.
Before using Contentful to archive release, show me what will change and ask for confirmation.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Contentful working from chat.
| Manual | ClawLink | |
|---|---|---|
| Connection flow | Register a Contentful app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Contentful through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Contentful. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right Contentful actions to the runtime in a format your agent can reliably use. | 106 tools for Contentful are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Contentful to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Contentful in the browser, and the 106 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Contentful skill but can't call the tools
The ClawHub skill teaches OpenClaw about Contentful, but the calls run through the ClawLink plugin and your connected account. Make sure Contentful is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Connection succeeds but no tools appear
Reconnect Contentful from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling Contentful tools
Contentful tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Contentful call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
Contentful returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
OAuth finished in the browser but the account is still missing
Try reconnecting Contentful and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete.
FAQ
Is there a OpenClaw Contentful integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Contentful: link your Contentful account once in the browser and OpenClaw can call the Contentful API through 106 ready-made tools — no custom code or token handling.
How do I add Contentful to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Contentful skill from ClawHub, then you click Connect in the dashboard to authorize Contentful. OpenClaw calls the tools from the next message — no config files or API keys to manage.
How long does it take to connect Contentful to OpenClaw?
About two minutes. Sign in, click Connect next to Contentful in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Contentful up myself?
The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Contentful working from chat.
OpenClaw installed the Contentful skill but can't call the tools
The ClawHub skill teaches OpenClaw about Contentful, but the calls run through the ClawLink plugin and your connected account. Make sure Contentful is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Related
GitHub
Manage repositories, issues, pull requests, and workflows
OpenClaw PagerDuty integration
Manage incidents, on-call schedules, and services
OpenClaw SafetyCulture integration
SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.