How to connect Lusha to OpenClaw
Connect Lusha to OpenClaw with ClawLink: paste your Lusha key once and 67 tools work from chat. No MCP server to run, nothing stored on your machine.

B2B 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.
- 1
Install 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:
Use Lusha to enrich contacts 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:
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 67 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 67 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
67 Lusha 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 67.
30 of 67 Lusha tools for OpenClaw
| Tool | What it does |
|---|---|
Enrich contacts lusha_enrich_contacts | Reveal contact data, optionally using BYOK Data Waterfall providers |
Find buying group contacts lusha_find_buying_group_contacts | Identify and score buying-group contacts within target companies |
Get account usage lusha_get_account_usage | Retrieve the connected Lusha account's usage, limits, plan, and pricing |
Get audit log stats lusha_get_audit_log_stats | Retrieve aggregated audit-log delivery statistics, including total, successful and failed |
Get audit logs lusha_get_audit_logs | Retrieve account audit logs for API calls and webhook deliveries to review delivery status |
Get companies table lusha_get_companies_table | Get a companies table's metadata, status, counts, and columns |
Get companies table entities lusha_get_companies_table_entities | Read a page of company rows and column values from a table |
Get company filter values lusha_get_company_filter_values | Retrieve valid values for one Lusha company prospecting filter |
Get company icp fit scores lusha_get_company_icp_fit_scores | Score companies against the connected user's Target Profiles |
Get company recommendations lusha_get_company_recommendations | Return companies ranked for the user by Target Profiles and recent signals |
Get company signal filter values lusha_get_company_signal_filter_values | Retrieve valid values for one company signal filter |
Get company signal scores lusha_get_company_signal_scores | Score companies by active buying signals |
Get contact filter values lusha_get_contact_filter_values | Retrieve valid values for one contact prospecting filter |
Get contact icp fit scores lusha_get_contact_icp_fit_scores | Score contacts against user-owned or shared Lusha Target Profiles |
Get contact recommendations lusha_get_contact_recommendations | Return a user's contacts ranked against Target Profiles and recent signals |
Get contact signal scores lusha_get_contact_signal_scores | Score contacts from zero to one by their active buying signals |
Get contacts enrich job lusha_get_contacts_enrich_job | Poll one async contact Data Waterfall job without incurring a polling charge |
Get contacts table lusha_get_contacts_table | Get a contacts table's metadata, entity count, processing status, and columns with row-status |
Get contacts table entities lusha_get_contacts_table_entities | Read one page of contacts and column values from a table |
Get conversation transcript lusha_get_conversation_transcript | Fetch the speaker-attributed transcript for one conversation |
Get subscription lusha_get_subscription | Retrieve a webhook subscription by ID, including its status, configuration, and entity details |
Get website visits lusha_get_website_visits | Return companies ranked by visits to the connected user's tracked sites |
List companies column catalog lusha_list_companies_column_catalog | List Lusha columns that can be added to a companies table |
List companies tables lusha_list_companies_tables | List company tables visible to the resolved owner |
List company filter types lusha_list_company_filter_types | List company prospecting filters and their query requirements |
List company recommendation filters lusha_list_company_recommendation_filters | List Target Profiles and signals available to company recommendations |
List company signal filters lusha_list_company_signal_filters | List company signal filters and their query requirements |
List company signal types lusha_list_company_signal_types | List all supported company signal types |
List contact filter types lusha_list_contact_filter_types | Discover contact prospecting filter types and their query requirements |
List contact recommendation filters lusha_list_contact_recommendation_filters | List the Target Profiles and signals available to the current user's recommendations |
Try it: find the Lusha tool you need
Browse the 30 Lusha tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use Lusha to enrich contacts and walk me through the result in plain English.
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. | 67 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 67 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 67 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.
Related
SendPulse
SendPulse is a multichannel marketing platform for email, SMS, chatbots, CRM, automation, web push, and transactional messaging.
HighLevel Location
HighLevel provides Location-scoped CRM, marketing, conversations, calendars, payments, and business automation APIs.
OpenClaw ActiveCampaign integration
Marketing automation, CRM, and email marketing