# How to connect Enrich to OpenClaw (paste one key, 14 tools) > Connect Enrich to OpenClaw with ClawLink: paste your Enrich key once and 14 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/enrich The usual route to Enrich 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 Enrich setup: install one ClawHub skill, connect Enrich in the browser, and OpenClaw can call real Enrich 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 Enrich. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Enrich** — 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 enrich # connect Enrich (browser OAuth) npx -y @useclawlink/cli actions enrich # list available actions npx -y @useclawlink/cli run enrich --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 Enrich in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Enrich API key once. Verify the connection by asking OpenClaw: > Use Enrich to count 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 Enrich is connected in the dashboard, that agent calls the same 14 Enrich 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). ## Enrich MCP for OpenClaw Looking for a Enrich MCP server for OpenClaw? ClawLink connects Enrich to OpenClaw and exposes 14 Enrich 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 Enrich integration](https://claw-link.dev/hermes/enrich) works the same way. ## What the OpenClaw Enrich integration can do 14 Enrich tools are ready for OpenClaw once the account is connected. ### All 14 Enrich tools for OpenClaw | Tool | What it does | |---|---| | **Count leads** `enrich_count_leads` | Count leads matching Enrich Lead Finder filters without returning lead records | | **Find company employees** `enrich_find_company_employees` | Find employees at a company from its LinkedIn URL, optionally filtering by geography and role | | **Find work email** `enrich_find_work_email` | Find a person's professional email from their first name, last name, and company domain | | **Get credit balance** `enrich_get_credit_balance` | Return the connected organization's current Enrich credit balance and the time it was measured | | **Get lead filter options** `enrich_get_lead_filter_options` | Return Enrich's current Lead Finder option catalog, keyed by filter name, for constructing | | **List credit transactions** `enrich_list_credit_transactions` | Return one page of credit top-ups and charges for the connected organization, optionally | | **Lookup person by email** `enrich_lookup_person_by_email` | Look up a professional profile from one email address | | **Resume batch** `enrich_resume_batch` | Recover an existing validation, work-email, or people-lookup batch after a timeout or | | **Search company icp** `enrich_search_company_icp` | Run Enrich's ranked cascade search for ideal-customer-profile employees at one company | | **Search leads** `enrich_search_leads` | Return one page of leads matching Lead Finder filters | | **Validate email** `enrich_validate_email` | Check one email address for deliverability and return Enrich's result, confidence, provider | | **Batch find work emails** `enrich_batch_find_work_emails` | Submit 1-100 people for asynchronous work-email finding, reserve up to 10 credits per | | **Batch lookup people by email** `enrich_batch_lookup_people_by_email` | Submit 1-100 emails for asynchronous professional-profile lookup, reserve up to 10 credits per | | **Batch validate emails** `enrich_batch_validate_emails` | Submit 1-100 emails as one asynchronous Enrich validation batch, reserving up to 1 credit per | ## Example prompts **Count Leads** > Use Enrich to count leads and walk me through the result in plain English. **Find Company Employees** > Use Enrich to find company employees and walk me through the result in plain English. **Find Work Email** > Use Enrich to find work email and walk me through the result in plain English. **Get Credit Balance** > Pull the relevant data from Enrich, summarize it in plain English, and point out anything that needs attention. ## ClawLink vs. building it yourself 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 Enrich working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Enrich API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Enrich account becomes available to the agent without you building credential management. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Enrich. | 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 Enrich actions to the runtime in a format your agent can reliably use. | 14 tools for Enrich are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Enrich 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 Enrich in the browser, and the 14 tools above work from chat. There is no SDK and no config file, and the Enrich key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Enrich skill but can't call the tools The ClawHub skill teaches OpenClaw about Enrich, but the calls run through the ClawLink plugin and your connected account. Make sure Enrich 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 Enrich 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 Enrich tools Enrich 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 Enrich 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. ### Enrich 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 Enrich has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Enrich integration? Yes. ClawLink is the fastest way to connect OpenClaw to Enrich: link your Enrich account once in the browser and OpenClaw can call the Enrich API through 14 ready-made tools — no custom code or token handling. ### How do I add Enrich to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Enrich skill from ClawHub, then you click Connect in the dashboard to authorize Enrich. OpenClaw calls the tools from the next message — no config files, and the Enrich key you paste is stored server-side instead of in your environment. ### How long does it take to connect Enrich to OpenClaw? About two minutes. Sign in, click Connect next to Enrich in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Enrich 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 Enrich working from chat. ### OpenClaw installed the Enrich skill but can't call the tools The ClawHub skill teaches OpenClaw about Enrich, but the calls run through the ClawLink plugin and your connected account. Make sure Enrich 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 - [Connect DataRobot](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. - [Connect Chatbotkit](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. - [OpenClaw Just One API integration](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.