# How to connect Heyreach to OpenClaw (paste one key, 19 tools) > Connect Heyreach to OpenClaw with ClawLink: paste your Heyreach key once and 19 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/heyreach The usual route to Heyreach 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 Heyreach setup: install one ClawHub skill, connect Heyreach in the browser, and OpenClaw can call real Heyreach 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 Heyreach. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Heyreach** — 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 heyreach # connect Heyreach (browser OAuth) npx -y @useclawlink/cli actions heyreach # list available actions npx -y @useclawlink/cli run heyreach --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 Heyreach in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Heyreach API key once. Verify the connection by asking OpenClaw: > Use Heyreach to check api key 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 Heyreach is connected in the dashboard, that agent calls the same 19 Heyreach 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). ## Heyreach MCP for OpenClaw Looking for a Heyreach MCP server for OpenClaw? ClawLink connects Heyreach to OpenClaw and exposes 19 Heyreach 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 Heyreach integration](https://claw-link.dev/hermes/heyreach) works the same way. ## What the OpenClaw Heyreach integration can do 19 Heyreach tools are ready for OpenClaw once the account is connected. The 18 below are the ones people reach for most; your agent can call all 19. ### 18 of 19 Heyreach tools for OpenClaw | Tool | What it does | |---|---| | **Check API key** `heyreach_check_api_key` | Check if the API key is valid | | **Get all campaigns** `heyreach_get_all_campaigns` | Retrieve all campaigns | | **Get all leads** `heyreach_get_all_leads` | Retrieve all leads in a HeyReach list | | **Get all linkedin accounts** `heyreach_get_all_linkedin_accounts` | Retrieve all LinkedIn accounts | | **Get all lists** `heyreach_get_all_lists` | Retrieve all lists | | **Get all webhooks** `heyreach_get_all_webhooks` | Retrieve all webhooks | | **Get companies from list** `heyreach_get_companies_from_list` | Get companies from a company list | | **Get conversations v2** `heyreach_get_conversations_v2` | Retrieve paginated LinkedIn conversations with advanced filters | | **Get lead** `heyreach_get_lead` | Retrieve detailed information for a lead by profile URL | | **Get lists for lead** `heyreach_get_lists_for_lead` | Retrieve all lists that contain a specific lead by profile URL | | **Get my network for sender** `heyreach_get_my_network_for_sender` | Get the LinkedIn network for a specified sender account | | **Get overall stats** `heyreach_get_overall_stats` | Get overall statistics for LinkedIn accounts and campaigns | | **Get webhook by ID** `heyreach_get_webhook_by_id` | Retrieve a webhook by its ID | | **Add leads to list v2** `heyreach_add_leads_to_list_v2` | Add leads to a lead list in HeyReach for LinkedIn campaigns | | **Create empty list** `heyreach_create_empty_list` | Create an empty list | | **Create tags** `heyreach_create_tags` | Create one or multiple tags for your workspace | | **Create webhook** `heyreach_create_webhook` | Create a new webhook | | **Update webhook** `heyreach_update_webhook` | Update an existing webhook’s configuration | ## Example prompts **Check Api Key** > Use Heyreach to check api key and walk me through the result in plain English. **Get All Campaigns** > Pull the relevant data from Heyreach, summarize it in plain English, and point out anything that needs attention. **Get All Leads** > Pull the relevant data from Heyreach, summarize it in plain English, and point out anything that needs attention. **Get All Linkedin Accounts** > Pull the relevant data from Heyreach, 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 Heyreach working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Heyreach API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Heyreach 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 Heyreach. | 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 Heyreach actions to the runtime in a format your agent can reliably use. | 19 tools for Heyreach are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Heyreach 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 Heyreach in the browser, and the 19 tools above work from chat. There is no SDK and no config file, and the Heyreach 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 Heyreach skill but can't call the tools The ClawHub skill teaches OpenClaw about Heyreach, but the calls run through the ClawLink plugin and your connected account. Make sure Heyreach 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 Heyreach 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 Heyreach tools Heyreach 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 Heyreach 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. ### Heyreach 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 Heyreach has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Heyreach integration? Yes. ClawLink is the fastest way to connect OpenClaw to Heyreach: link your Heyreach account once in the browser and OpenClaw can call the Heyreach API through 19 ready-made tools — no custom code or token handling. ### How do I add Heyreach to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Heyreach skill from ClawHub, then you click Connect in the dashboard to authorize Heyreach. OpenClaw calls the tools from the next message — no config files, and the Heyreach key you paste is stored server-side instead of in your environment. ### How long does it take to connect Heyreach to OpenClaw? About two minutes. Sign in, click Connect next to Heyreach in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Heyreach 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 Heyreach working from chat. ### OpenClaw installed the Heyreach skill but can't call the tools The ClawHub skill teaches OpenClaw about Heyreach, but the calls run through the ClawLink plugin and your connected account. Make sure Heyreach 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 - [ActiveCampaign](https://claw-link.dev/openclaw/activecampaign) — Marketing automation, CRM, and email marketing - [Benchmark Email](https://claw-link.dev/openclaw/benchmark-email) — Benchmark Email is a comprehensive email marketing platform offering tools for creating, sending, and analyzing email campaigns. - [Mailchimp](https://claw-link.dev/openclaw/mailchimp) — Create email campaigns and manage audiences