How to connect Fullenrich to OpenClaw
Connect Fullenrich to OpenClaw with ClawLink: paste your Fullenrich key once and 9 tools work from chat. No MCP server to run, nothing stored on your machine.
FullenrichAPI KEYMCPFullEnrich is a B2B email and phone waterfall enrichment platform that aggregates contact information from over 15 premium vendors to find the emails and phone numbers of leads.. Once connected, OpenClaw can read and act on Fullenrich from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Fullenrich 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 Fullenrich setup: install one ClawHub skill, connect Fullenrich in the browser, and OpenClaw can call real Fullenrich 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 Fullenrich.
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 Fullenrich
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Fullenrich?"
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 Fullenrich in the ClawLink dashboard — paste your Fullenrich API key once.
Verify the connection by asking OpenClaw:
Create it in Fullenrich for me, then confirm the important fields before you finish.
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 Fullenrich is connected in the dashboard, that agent calls the same 9 Fullenrich tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Fullenrich MCP for OpenClaw
Looking for a Fullenrich MCP server for OpenClaw? ClawLink connects Fullenrich to OpenClaw and exposes 9 Fullenrich tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Fullenrich integration works the same way.
What the OpenClaw Fullenrich integration can do
9 Fullenrich tools are ready for OpenClaw once the account is connected.
All 9 Fullenrich tools for OpenClaw
| Tool | What it does |
|---|---|
Create contact data list fullenrich_create_contact_data_list | Create a list of contact data entries |
Get current credit balance fullenrich_get_current_credit_balance | Retrieve current workspace credit balance |
Get enrichment result fullenrich_get_enrichment_result | Retrieve results of a bulk enrichment by enrichment ID |
Get reverse email result fullenrich_get_reverse_email_result | Retrieve results from a reverse email lookup operation using reverse email ID |
Search company fullenrich_search_company | Search for companies based on filters including name, domain, industry, type, headquarters |
Search people fullenrich_search_people | Search for people based on filters including company, location, skills, position titles, and |
Verify API key fullenrich_verify_api_key | Check if your API key is valid and return the associated workspace ID |
Reverse email lookup fullenrich_reverse_email_lookup | Perform bulk reverse email lookup to retrieve full person and company profile from work or |
Start bulk enrichment fullenrich_start_bulk_enrichment | Start a bulk enrichment job |
Try it: find the Fullenrich tool you need
Browse the 9 Fullenrich tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Create it in Fullenrich for me, then confirm the important fields before you finish.
Pull the relevant data from Fullenrich, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Fullenrich, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Fullenrich, 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 Fullenrich working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Fullenrich API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Fullenrich 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 Fullenrich. | 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 Fullenrich actions to the runtime in a format your agent can reliably use. | 9 tools for Fullenrich are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Fullenrich 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 Fullenrich in the browser, and the 9 tools above work from chat. There is no SDK and no config file, and the Fullenrich 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 Fullenrich skill but can't call the tools
The ClawHub skill teaches OpenClaw about Fullenrich, but the calls run through the ClawLink plugin and your connected account. Make sure Fullenrich 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 Fullenrich 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 Fullenrich tools
Fullenrich 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 Fullenrich 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.
Fullenrich 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 Fullenrich 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 Fullenrich integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Fullenrich: link your Fullenrich account once in the browser and OpenClaw can call the Fullenrich API through 9 ready-made tools — no custom code or token handling.
How do I add Fullenrich to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Fullenrich skill from ClawHub, then you click Connect in the dashboard to authorize Fullenrich. OpenClaw calls the tools from the next message — no config files, and the Fullenrich key you paste is stored server-side instead of in your environment.
How long does it take to connect Fullenrich to OpenClaw?
About two minutes. Sign in, click Connect next to Fullenrich in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Fullenrich 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 Fullenrich working from chat.
OpenClaw installed the Fullenrich skill but can't call the tools
The ClawHub skill teaches OpenClaw about Fullenrich, but the calls run through the ClawLink plugin and your connected account. Make sure Fullenrich 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.
