# How to connect Clarify to OpenClaw (no API keys) > Connect Clarify to OpenClaw with ClawLink in one click — 46 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup. Web version: https://claw-link.dev/openclaw/clarify The usual route to Clarify 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 Clarify setup: install one ClawHub skill, connect Clarify in the browser, and OpenClaw can call real Clarify 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 Clarify. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Clarify** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect clarify # connect Clarify (browser OAuth) npx -y @useclawlink/cli actions clarify # list available actions npx -y @useclawlink/cli run clarify --input '' # execute (add --confirm for writes) ``` ### 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: ```bash 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 Clarify in the [ClawLink dashboard](https://claw-link.dev/dashboard) — a one-click OAuth approval, no API keys. Verify the connection by asking OpenClaw: > Use Clarify to mcp find leads 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: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Clarify is connected in the dashboard, that agent calls the same 46 Clarify tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Clarify MCP for OpenClaw Looking for a Clarify MCP server for OpenClaw? ClawLink connects Clarify to OpenClaw and exposes 46 Clarify tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes Clarify integration](https://claw-link.dev/hermes/clarify) works the same way. ## What the OpenClaw Clarify integration can do 46 Clarify 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 46. ### 30 of 46 Clarify tools for OpenClaw | Tool | What it does | |---|---| | **Mcp find leads** `clarify_mcp_find_leads` | Search Clarify's built-in prospect database of companies and people to find new leads matching | | **Mcp get agent runs** `clarify_mcp_get_agent_runs` | List an agent's runs, executions, invocations, and past run history, or fetch one run with its | | **Mcp get agents** `clarify_mcp_get_agents` | List agents visible to the current user, or fetch a single agent by ID | | **Mcp get artifact component doc** `clarify_mcp_get_artifact_component_doc` | Get the full prop contract for one or more Clarify design-system components available to | | **Mcp get artifact source** `clarify_mcp_get_artifact_source` | Read the current source of an existing artifact — the JSX of its applied version, plus its name | | **Mcp get calendar events** `clarify_mcp_get_calendar_events` | List the current user's calendar events in a time range | | **Mcp get campaign recipients** `clarify_mcp_get_campaign_recipients` | List the individual people enrolled in a campaign, with their per-person engagement — who | | **Mcp get campaigns** `clarify_mcp_get_campaigns` | List campaigns in the workspace, or fetch a single campaign by ID with full details | | **Mcp get current user** `clarify_mcp_get_current_user` | Get information about the current authenticated user, including their timezone | | **Mcp get lists** `clarify_mcp_get_lists` | Get list metadata (saved views) for an entity type, or fetch a single list by ID | | **Mcp get records** `clarify_mcp_get_records` | Retrieve detailed information about specific records by their IDs | | **Mcp get schema** `clarify_mcp_get_schema` | Get the schema for Clarify entities | | **Mcp get workflow runs** `clarify_mcp_get_workflow_runs` | Get execution runs for a workflow | | **Mcp get workflows** `clarify_mcp_get_workflows` | Get and search workflows in the workspace, or fetch a single workflow with its full | | **Mcp query analytics** `clarify_mcp_query_analytics` | Execute read-only ClickHouse SQL against the analytics event log | | **Mcp query data** `clarify_mcp_query_data` | Execute PostgreSQL queries to retrieve data from Clarify | | **Mcp read context** `clarify_mcp_read_context` | Read Clarify product knowledge and documentation | | **Mcp add comment** `clarify_mcp_add_comment` | Add a comment to a supported entity | | **Mcp create campaign** `clarify_mcp_create_campaign` | Create a new email campaign (sequence) in DRAFT mode | | **Mcp create email draft** `clarify_mcp_create_email_draft` | Create an email draft in the user's connected Gmail or Outlook account for them to review | | **Mcp import leads** `clarify_mcp_import_leads` | Import leads from a tam_company or tam_person search into Clarify | | **Mcp import meeting transcript** `clarify_mcp_import_meeting_transcript` | Import a meeting transcript from an external source (Granola, Notion, Circleback) | | **Mcp respond to calendar event** `clarify_mcp_respond_to_calendar_event` | RSVP to a calendar event you've been invited to | | **Mcp send email** `clarify_mcp_send_email` | Send an email immediately through the user's connected email account | | **Mcp submit feedback** `clarify_mcp_submit_feedback` | Submit concise feature requests or feedback about MCP tools | | **Mcp create or update agent** `clarify_mcp_create_or_update_agent` | Create or update an agent, an autonomous AI assistant | | **Mcp create or update artifact** `clarify_mcp_create_or_update_artifact` | Create a new artifact or write a new version to an existing artifact | | **Mcp create or update calendar event** `clarify_mcp_create_or_update_calendar_event` | Create a new calendar event or update an existing one | | **Mcp create or update custom object** `clarify_mcp_create_or_update_custom_object` | Create a new custom object type or update an existing one in the workspace | | **Mcp create or update fields** `clarify_mcp_create_or_update_fields` | Create new fields or update existing field metadata (name, options, AI config) on any entity | ## Example prompts **Mcp Find Leads** > Use Clarify to mcp find leads and walk me through the result in plain English. **Mcp Get Agent Runs** > Use Clarify to mcp get agent runs and walk me through the result in plain English. **Mcp Get Agents** > Use Clarify to mcp get agents and walk me through the result in plain English. **Mcp Get Artifact Component Doc** > Use Clarify to mcp get artifact component doc 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 Clarify working from chat. | | Manual | ClawLink | |---|---|---| | **Connection flow** | Register a Clarify app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Clarify 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 Clarify. | 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 Clarify actions to the runtime in a format your agent can reliably use. | 46 tools for Clarify are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Clarify 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 Clarify in the browser, and the 46 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](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Clarify skill but can't call the tools The ClawHub skill teaches OpenClaw about Clarify, but the calls run through the ClawLink plugin and your connected account. Make sure Clarify 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 Clarify 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 Clarify tools Clarify 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 Clarify 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. ### Clarify 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 Clarify and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete. ### Is there a OpenClaw Clarify integration? Yes. ClawLink is the fastest way to connect OpenClaw to Clarify: link your Clarify account once in the browser and OpenClaw can call the Clarify API through 46 ready-made tools — no custom code or token handling. ### How do I add Clarify to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Clarify skill from ClawHub, then you click Connect in the dashboard to authorize Clarify. OpenClaw calls the tools from the next message — no config files or API keys to manage. ### How long does it take to connect Clarify to OpenClaw? About two minutes. Sign in, click Connect next to Clarify in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Clarify 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 Clarify working from chat. ### OpenClaw installed the Clarify skill but can't call the tools The ClawHub skill teaches OpenClaw about Clarify, but the calls run through the ClawLink plugin and your connected account. Make sure Clarify 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 - [OpenClaw DataRobot integration](https://claw-link.dev/openclaw/datarobot) — DataRobot is a machine learning platform that automates model building, deployment, and monitoring, enabling organizations to derive predictive insights from large datasets. - [Chatbotkit tools](https://claw-link.dev/openclaw/chatbotkit) — 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 tools](https://claw-link.dev/openclaw/just-one-api) — Just One API provides unified access to public social media, creator, entertainment, and ecommerce data across hundreds of metered endpoints.