How to connect Icypeas to OpenClaw
Connect Icypeas to OpenClaw with ClawLink: paste your Icypeas key once and 22 tools work from chat. No MCP server to run, nothing stored on your machine.
IcypeasAPI KEYMCPIcypeas is an email discovery and verification tool that allows users to find and verify professional email addresses using first name, last name, and company domain.. Once connected, OpenClaw can read and act on Icypeas from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Icypeas 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 Icypeas setup: install one ClawHub skill, connect Icypeas in the browser, and OpenClaw can call real Icypeas 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 Icypeas.
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 Icypeas
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Icypeas?"
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 Icypeas in the ClawLink dashboard — paste your Icypeas API key once.
Verify the connection by asking OpenClaw:
Use Icypeas to bulk find profile urls 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 Icypeas is connected in the dashboard, that agent calls the same 22 Icypeas tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Icypeas MCP for OpenClaw
Looking for a Icypeas MCP server for OpenClaw? ClawLink connects Icypeas to OpenClaw and exposes 22 Icypeas tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Icypeas integration works the same way.
What the OpenClaw Icypeas integration can do
22 Icypeas tools are ready for OpenClaw once the account is connected.
All 22 Icypeas tools for OpenClaw
| Tool | What it does |
|---|---|
Bulk find profile URLS icypeas_bulk_find_profile_urls | Perform bulk search for profile URLs based on firstname, lastname, and company/domain or job |
Bulk reverse email lookup icypeas_bulk_reverse_email_lookup | Find LinkedIn profile URLs for multiple professional email addresses in a single request |
Check progress icypeas_check_progress | Check the processing progress of a search by its ID |
Count companies icypeas_count_companies | Count companies in Icypeas database matching specified filters without returning data or being |
Count people icypeas_count_people | Count people matching specified filters without retrieving data or consuming credits |
Fetch bulk search info icypeas_fetch_bulk_search_info | Retrieve bulk search files with their status and progress |
Fetch subscription info icypeas_fetch_subscription_info | Retrieves subscription details and remaining credits for an Icypeas account |
Find companies icypeas_find_companies | Search companies in Icypeas database |
Find linkedin profile by email icypeas_find_linkedin_profile_by_email | Find the LinkedIn profile URL behind a single professional email address |
Find people icypeas_find_people | Search for people/leads in the Icypeas database |
Find profile URL icypeas_find_profile_url | Finds a person's LinkedIn profile URL using their name and company or job title |
Parse bulk search statistics icypeas_parse_bulk_search_statistics | Parse bulk search statistics webhook |
Retrieve search results icypeas_retrieve_search_results | Retrieve the results of a search by ID or to paginate through bulk search results |
Setup notifications icypeas_setup_notifications | Provides instructions for setting up Icypeas push notifications/webhooks |
Bulk email search icypeas_bulk_email_search | Initiate a bulk email search job to find professional email addresses for multiple people at |
Bulk scrape icypeas_bulk_scrape | Scrape multiple LinkedIn profiles or companies in bulk (up to 50 per request) |
Domain scan icypeas_domain_scan | Scan a domain for role-based email addresses |
Find company URL icypeas_find_company_url | Find a single company profile URL using a company name or domain |
Find single email icypeas_find_single_email | Initiates an asynchronous email search to find a prospect's email address using their name and |
Scrape company icypeas_scrape_company | Initiate scraping of a LinkedIn company page |
Scrape profile icypeas_scrape_profile | Initiate scraping of a LinkedIn profile |
Verify email icypeas_verify_email | Verify if a specific email address exists and is valid |
Try it: find the Icypeas tool you need
Browse the 22 Icypeas tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use Icypeas to bulk find profile urls and walk me through the result in plain English.
Use Icypeas to bulk reverse email lookup and walk me through the result in plain English.
Use Icypeas to check progress and walk me through the result in plain English.
Use Icypeas to count companies 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 Icypeas working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Icypeas API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Icypeas 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 Icypeas. | 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 Icypeas actions to the runtime in a format your agent can reliably use. | 22 tools for Icypeas are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Icypeas 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 Icypeas in the browser, and the 22 tools above work from chat. There is no SDK and no config file, and the Icypeas 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 Icypeas skill but can't call the tools
The ClawHub skill teaches OpenClaw about Icypeas, but the calls run through the ClawLink plugin and your connected account. Make sure Icypeas 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 Icypeas 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 Icypeas tools
Icypeas 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 Icypeas 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.
Icypeas 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 Icypeas 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 Icypeas integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Icypeas: link your Icypeas account once in the browser and OpenClaw can call the Icypeas API through 22 ready-made tools — no custom code or token handling.
How do I add Icypeas to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Icypeas skill from ClawHub, then you click Connect in the dashboard to authorize Icypeas. OpenClaw calls the tools from the next message — no config files, and the Icypeas key you paste is stored server-side instead of in your environment.
How long does it take to connect Icypeas to OpenClaw?
About two minutes. Sign in, click Connect next to Icypeas in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Icypeas 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 Icypeas working from chat.
OpenClaw installed the Icypeas skill but can't call the tools
The ClawHub skill teaches OpenClaw about Icypeas, but the calls run through the ClawLink plugin and your connected account. Make sure Icypeas 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.
