ClawLink

How to connect Twenty to OpenClaw

Connect Twenty to OpenClaw with ClawLink: paste your Twenty key once and 16 tools work from chat. No MCP server to run, nothing stored on your machine.

Get started for free
OpenClaw
OpenClaw
ClawLink
ClawLink
Twenty
Twenty
TwentyAPI KEYMCP

The #1 Open-Source CRM.. Once connected, OpenClaw can read and act on Twenty from chat — pairing, token refresh, and tool wiring handled for you.

23 tools

The usual route to Twenty 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 Twenty setup: install one ClawHub skill, connect Twenty in the browser, and OpenClaw can call real Twenty actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.

Setup

It takes three steps to connect OpenClaw to Twenty.

  1. 1

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

    Connect Twenty

    Paste your API key in the dashboard.

  3. 3

    Use it from chat

    Ask OpenClaw: "What can you do with Twenty?"

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-plugin

Then 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 Twenty in the ClawLink dashboard — paste your Twenty API key once.

Verify the connection by asking OpenClaw:

Pull the relevant data from Twenty, summarize it in plain English, and point out anything that needs attention.

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 login

login opens the same browser approval and stores a credential locally. Once Twenty is connected in the dashboard, that agent calls the same 16 Twenty tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.

Twenty MCP for OpenClaw

Looking for a Twenty MCP server for OpenClaw? ClawLink connects Twenty to OpenClaw and exposes 16 Twenty tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Twenty integration works the same way.

What the OpenClaw Twenty integration can do

16 Twenty tools are ready for OpenClaw once the account is connected. The 15 below are the ones people reach for most; your agent can call all 16.

15 of 16 Twenty tools for OpenClaw

ToolWhat it does
Get custom record twenty_get_custom_recordGet one record from a workspace-defined custom object by UUID using the object's plural API
Get record twenty_get_recordGet one company, person, opportunity, or task by its Twenty UUID, optionally including direct
List custom records twenty_list_custom_recordsList records from a workspace-defined custom object using its plural API name, with Twenty
List fields twenty_list_fieldsList field definitions from the connected Twenty workspace to discover exact field names
List note targets twenty_list_note_targetsList associations between notes and companies, people, or opportunities with Twenty filtering
List objects twenty_list_objectsList standard and custom object definitions in the connected Twenty workspace for schema
List records twenty_list_recordsList companies, people, opportunities, or tasks with Twenty filter syntax, ordering, relation
List task targets twenty_list_task_targetsList associations between tasks and companies, people, or opportunities with Twenty filtering
List workspace members twenty_list_workspace_membersList Twenty workspace members for identity and assignment lookups, with filtering, ordering
Batch create records twenty_batch_create_recordsCreate 1-60 records of one type
Create attached note twenty_create_attached_noteCreate a note and attach it to one company, person, or opportunity
Create custom record twenty_create_custom_recordCreate one record in a workspace-defined custom object using its plural API name and arbitrary
Create record twenty_create_recordCreate one company, person, opportunity, or task using the supported standard fields in the
Update custom record twenty_update_custom_recordPartially update one record in a workspace-defined custom object by UUID
Update record twenty_update_recordPartially update one company, person, opportunity, or task by UUID using the supported standard

Try it: find the Twenty tool you need

Browse the 22 Twenty tools

Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.

Example prompts

Pull the relevant data from Twenty, summarize it in plain English, and point out anything that needs attention.

The alternative to ClawLink is usually manual API key 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 Twenty working from chat.

ManualClawLink
Credential handlingCollect, validate, store, and rotate the Twenty API key yourself, then make sure every tool call uses the right account.Users complete the hosted ClawLink setup once and the connected Twenty account becomes available to the agent without you building credential management.
Ongoing maintenanceYou own refresh logic, permission debugging, environment config, and every provider-specific edge case for Twenty.ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure.
Agent usabilityYou still need to expose the right Twenty actions to the runtime in a format your agent can reliably use.16 tools for Twenty are already exposed through ClawLink, so the agent can read and act from chat immediately.

Composio also exposes Twenty 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 Twenty in the browser, and the 16 tools above work from chat. There is no SDK and no config file, and the Twenty key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.

Troubleshooting

OpenClaw installed the Twenty skill but can't call the tools

The ClawHub skill teaches OpenClaw about Twenty, but the calls run through the ClawLink plugin and your connected account. Make sure Twenty 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 Twenty 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 Twenty tools

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

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

API key setup works but results look incomplete

Double-check that the API key for Twenty has the right scopes or account access. A valid key can still be too limited for some reads or writes.

FAQ

Is there a OpenClaw Twenty integration?

Yes. ClawLink is the fastest way to connect OpenClaw to Twenty: link your Twenty account once in the browser and OpenClaw can call the Twenty API through 16 ready-made tools — no custom code or token handling.

How do I add Twenty to OpenClaw with ClawLink?

Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Twenty skill from ClawHub, then you click Connect in the dashboard to authorize Twenty. OpenClaw calls the tools from the next message — no config files, and the Twenty key you paste is stored server-side instead of in your environment.

How long does it take to connect Twenty to OpenClaw?

About two minutes. Sign in, click Connect next to Twenty in the dashboard, authenticate, and OpenClaw can use it from the next chat message.

Why use ClawLink instead of wiring Twenty up myself?

The alternative to ClawLink is usually manual API key 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 Twenty working from chat.

OpenClaw installed the Twenty skill but can't call the tools

The ClawHub skill teaches OpenClaw about Twenty, but the calls run through the ClawLink plugin and your connected account. Make sure Twenty 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.

On this page