How to connect Leadfeeder to OpenClaw
Connect Leadfeeder to OpenClaw with ClawLink: paste your Leadfeeder key once and 6 tools work from chat. No MCP server to run, nothing stored on your machine.
LeadfeederAPI KEYMCPLeadfeeder identifies companies visiting your website and converts them into high-value leads.. Once connected, OpenClaw can read and act on Leadfeeder from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Leadfeeder 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 Leadfeeder setup: install one ClawHub skill, connect Leadfeeder in the browser, and OpenClaw can call real Leadfeeder 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 Leadfeeder.
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 Leadfeeder
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Leadfeeder?"
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 Leadfeeder in the ClawLink dashboard — paste your Leadfeeder API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from Leadfeeder, 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 loginlogin opens the same browser approval and stores a credential locally. Once Leadfeeder is connected in the dashboard, that agent calls the same 6 Leadfeeder tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Leadfeeder MCP for OpenClaw
Looking for a Leadfeeder MCP server for OpenClaw? ClawLink connects Leadfeeder to OpenClaw and exposes 6 Leadfeeder tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Leadfeeder integration works the same way.
What the OpenClaw Leadfeeder integration can do
6 Leadfeeder tools are ready for OpenClaw once the account is connected.
All 6 Leadfeeder tools for OpenClaw
| Tool | What it does |
|---|---|
Get account leadfeeder_get_account | Retrieve the details of a specific account by ID |
Get accounts leadfeeder_get_accounts | Retrieve a list of accounts the user has access to |
Get all visits leadfeeder_get_all_visits | Retrieve all visits for a specific lead |
Get company info by ip leadfeeder_get_company_info_by_ip | Retrieve company information based on an IP address |
Get custom feeds leadfeeder_get_custom_feeds | Retrieve all custom feeds configured for a Leadfeeder account |
Get tracking script leadfeeder_get_tracking_script | Retrieve the website tracking script for a given account |
Try it: find the Leadfeeder tool you need
Browse the 6 Leadfeeder 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 Leadfeeder, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Leadfeeder, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Leadfeeder, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Leadfeeder, 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 Leadfeeder working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Leadfeeder API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Leadfeeder 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 Leadfeeder. | 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 Leadfeeder actions to the runtime in a format your agent can reliably use. | 6 tools for Leadfeeder are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Leadfeeder 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 Leadfeeder in the browser, and the 6 tools above work from chat. There is no SDK and no config file, and the Leadfeeder 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 Leadfeeder skill but can't call the tools
The ClawHub skill teaches OpenClaw about Leadfeeder, but the calls run through the ClawLink plugin and your connected account. Make sure Leadfeeder 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 Leadfeeder 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 Leadfeeder tools
Leadfeeder 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 Leadfeeder 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.
Leadfeeder 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 Leadfeeder 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 Leadfeeder integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Leadfeeder: link your Leadfeeder account once in the browser and OpenClaw can call the Leadfeeder API through 6 ready-made tools — no custom code or token handling.
How do I add Leadfeeder to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Leadfeeder skill from ClawHub, then you click Connect in the dashboard to authorize Leadfeeder. OpenClaw calls the tools from the next message — no config files, and the Leadfeeder key you paste is stored server-side instead of in your environment.
How long does it take to connect Leadfeeder to OpenClaw?
About two minutes. Sign in, click Connect next to Leadfeeder in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Leadfeeder 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 Leadfeeder working from chat.
OpenClaw installed the Leadfeeder skill but can't call the tools
The ClawHub skill teaches OpenClaw about Leadfeeder, but the calls run through the ClawLink plugin and your connected account. Make sure Leadfeeder 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.
