How to connect Clay to OpenClaw
Connect Clay to OpenClaw with ClawLink in one click — 17 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup.


Clay MCP lets agents research companies and contacts, run enrichment providers and Clay functions, and return enriched prospect data for authorized workspaces.. Once connected, OpenClaw can read and act on Clay from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Clay 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 Clay setup: install one ClawHub skill, connect Clay in the browser, and OpenClaw can call real Clay actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Copy this prompt into OpenClaw, or open the Clay 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 "Clay" (hith3sh/clay-workspace) from ClawHub only after those checks pass.
Skill page: https://clawhub.ai/hith3sh/clay-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 Clay.
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 Clay
One-click OAuth in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Clay?"
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 Clay in the ClawLink dashboard — a one-click OAuth approval, no API keys.
Verify the connection by asking OpenClaw:
Use Clay to mcp ask question about accounts 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 Clay is connected in the dashboard, that agent calls the same 17 Clay tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Clay MCP for OpenClaw
Looking for a Clay MCP server for OpenClaw? ClawLink connects Clay to OpenClaw and exposes 17 Clay tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Clay integration works the same way.
What the OpenClaw Clay integration can do
17 Clay tools are ready for OpenClaw once the account is connected.
All 17 Clay tools for OpenClaw
| Tool | What it does |
|---|---|
Mcp ask question about accounts clay_mcp_ask_question_about_accounts | Ask a natural language question about one or more accounts available in Clay Audiences |
Mcp find and enrich company clay_mcp_find_and_enrich_company | Find and enrich a single company by domain or LinkedIn URL |
Mcp find and enrich contacts at company clay_mcp_find_and_enrich_contacts_at_company | Search for contacts at a company by role, title, name, or department |
Mcp find and enrich list of contacts clay_mcp_find_and_enrich_list_of_contacts | Find and enrich specific named contacts at their companies |
Mcp get credits available clay_mcp_get_credits_available | Check if credits are available for the workspace |
Mcp get current workspace clay_mcp_get_current_workspace | Report which Clay workspace this connection is pinned to |
Mcp get subroutine input options clay_mcp_get_subroutine_input_options | Fetch the available dropdown options for a subroutine input that has a configured options source |
Mcp get task clay_mcp_get_task | Get task status and results by task ID |
Mcp get task context clay_mcp_get_task_context | Retrieve the current state of a task — all entities, enrichment values, and statuses |
Mcp list subroutines clay_mcp_list_subroutines | List available functions |
Mcp query objects clay_mcp_query_objects | Query audience accounts, contacts, or deals using natural language |
Mcp track event clay_mcp_track_event | Track an analytics event with optional properties |
Mcp add company data points clay_mcp_add_company_data_points | Add data points to companies in an existing search |
Mcp add contact data points clay_mcp_add_contact_data_points | Add data points to contacts in an existing search |
Mcp run subroutine clay_mcp_run_subroutine | Execute a function on contacts/companies FROM AN EXISTING SEARCH (Company Address, Company |
Mcp run subroutine direct clay_mcp_run_subroutine_direct | Execute a custom function on one or more sets of provided inputs |
Mcp run subroutine no mapping clay_mcp_run_subroutine_no_mapping | Run a custom subroutine on search entities |
Try it: find the Clay tool you need
Browse the 17 Clay tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use Clay to mcp ask question about accounts and walk me through the result in plain English.
Use Clay to mcp find and enrich company and walk me through the result in plain English.
Use Clay to mcp find and enrich contacts at company and walk me through the result in plain English.
Use Clay to mcp find and enrich list of contacts and walk me through the result in plain English.
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 Clay working from chat.
| Manual | ClawLink | |
|---|---|---|
| Connection flow | Register a Clay app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Clay 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 Clay. | 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 Clay actions to the runtime in a format your agent can reliably use. | 17 tools for Clay are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Clay 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 Clay in the browser, and the 17 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 Clay skill but can't call the tools
The ClawHub skill teaches OpenClaw about Clay, but the calls run through the ClawLink plugin and your connected account. Make sure Clay 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 Clay 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 Clay tools
Clay 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 Clay 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.
Clay 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 Clay 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 Clay integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Clay: link your Clay account once in the browser and OpenClaw can call the Clay API through 17 ready-made tools — no custom code or token handling.
How do I add Clay to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Clay skill from ClawHub, then you click Connect in the dashboard to authorize Clay. OpenClaw calls the tools from the next message — no config files or API keys to manage.
How long does it take to connect Clay to OpenClaw?
About two minutes. Sign in, click Connect next to Clay in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Clay 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 Clay working from chat.
OpenClaw installed the Clay skill but can't call the tools
The ClawHub skill teaches OpenClaw about Clay, but the calls run through the ClawLink plugin and your connected account. Make sure Clay 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
DataRobot tools
DataRobot is a machine learning platform that automates model building, deployment, and monitoring, enabling organizations to derive predictive insights from large datasets.
Chatbotkit tools
ChatBotKit is a platform that enables developers to build and manage AI-powered chatbots, offering comprehensive APIs and SDKs for seamless integration into applications.
Just One API
Just One API provides unified access to public social media, creator, entertainment, and ecommerce data across hundreds of metered endpoints.