How to connect Lusha to OpenClaw
Connect Lusha to OpenClaw with ClawLink: paste your Lusha key once and 7 tools work from chat. No MCP server to run, nothing stored on your machine.
LushaAPI KEYMCPB2B contact enrichment and prospecting platform providing verified email addresses, phone numbers, and company information.. Once connected, OpenClaw can read and act on Lusha from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Lusha 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 Lusha setup: install one ClawHub skill, connect Lusha in the browser, and OpenClaw can call real Lusha 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 Lusha.
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 Lusha
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Lusha?"
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 Lusha in the ClawLink dashboard — paste your Lusha API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from Lusha, 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 Lusha is connected in the dashboard, that agent calls the same 7 Lusha tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Lusha MCP for OpenClaw
Looking for a Lusha MCP server for OpenClaw? ClawLink connects Lusha to OpenClaw and exposes 7 Lusha tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Lusha integration works the same way.
What the OpenClaw Lusha integration can do
7 Lusha tools are ready for OpenClaw once the account is connected. The 6 below are the ones people reach for most; your agent can call all 7.
6 of 7 Lusha tools for OpenClaw
| Tool | What it does |
|---|---|
Get audit log stats lusha_get_audit_log_stats | Retrieve aggregated statistics for audit logs |
Get audit logs lusha_get_audit_logs | Retrieve audit logs for your account including API calls and webhook deliveries |
Get subscription lusha_get_subscription | Get details of a specific webhook subscription by ID |
List subscriptions lusha_list_subscriptions | List all webhook subscriptions for your account with pagination support |
Create subscription lusha_create_subscription | Create one or more webhook subscriptions for real-time signal notifications |
Update subscription lusha_update_subscription | Update an existing webhook subscription configuration |
Try it: find the Lusha tool you need
Browse the 6 Lusha 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 Lusha, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Lusha, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Lusha, summarize it in plain English, and point out anything that needs attention.
List the relevant items in Lusha, group them by priority, and recommend what OpenClaw should do next.
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 Lusha working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Lusha API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Lusha 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 Lusha. | 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 Lusha actions to the runtime in a format your agent can reliably use. | 7 tools for Lusha are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Lusha 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 Lusha in the browser, and the 7 tools above work from chat. There is no SDK and no config file, and the Lusha 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 Lusha skill but can't call the tools
The ClawHub skill teaches OpenClaw about Lusha, but the calls run through the ClawLink plugin and your connected account. Make sure Lusha 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 Lusha 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 Lusha tools
Lusha 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 Lusha 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.
Lusha 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 Lusha 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 Lusha integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Lusha: link your Lusha account once in the browser and OpenClaw can call the Lusha API through 7 ready-made tools — no custom code or token handling.
How do I add Lusha to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Lusha skill from ClawHub, then you click Connect in the dashboard to authorize Lusha. OpenClaw calls the tools from the next message — no config files, and the Lusha key you paste is stored server-side instead of in your environment.
How long does it take to connect Lusha to OpenClaw?
About two minutes. Sign in, click Connect next to Lusha in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Lusha 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 Lusha working from chat.
OpenClaw installed the Lusha skill but can't call the tools
The ClawHub skill teaches OpenClaw about Lusha, but the calls run through the ClawLink plugin and your connected account. Make sure Lusha 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.
