# How to connect Findymail to OpenClaw (paste one key, 21 tools) > Connect Findymail to OpenClaw with ClawLink: paste your Findymail key once and 21 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/findymail The usual route to Findymail 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 Findymail setup: install one ClawHub skill, connect Findymail in the browser, and OpenClaw can call real Findymail 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 Findymail. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Findymail** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect findymail # connect Findymail (browser OAuth) npx -y @useclawlink/cli actions findymail # list available actions npx -y @useclawlink/cli run findymail --input '' # execute (add --confirm for writes) ``` ### 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: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then 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 Findymail in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Findymail API key once. Verify the connection by asking OpenClaw: > Use Findymail to find email by name 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: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Findymail is connected in the dashboard, that agent calls the same 21 Findymail tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Findymail MCP for OpenClaw Looking for a Findymail MCP server for OpenClaw? ClawLink connects Findymail to OpenClaw and exposes 21 Findymail tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes Findymail integration](https://claw-link.dev/hermes/findymail) works the same way. ## What the OpenClaw Findymail integration can do 21 Findymail tools are ready for OpenClaw once the account is connected. The 19 below are the ones people reach for most; your agent can call all 21. ### 19 of 21 Findymail tools for OpenClaw | Tool | What it does | |---|---| | **Find email by name** `findymail_find_email_by_name` | Find someone's email using their full name and company domain | | **Get contact lists** `findymail_get_contact_lists` | Retrieve all contact lists | | **Get credits** `findymail_get_credits` | Check available API credits for your Findymail account | | **Get credits summary** `findymail_get_credits_summary` | Retrieve credits usage summary report for the authenticated account | | **Get credits team summary** `findymail_get_credits_team_summary` | Retrieve team credits usage summary report | | **Get exclusion list** `findymail_get_exclusion_list` | Retrieve a specific exclusion list by ID | | **Get intellimatch data** `findymail_get_intellimatch_data` | Retrieve data from an Intellimatch search | | **Get intellimatch status** `findymail_get_intellimatch_status` | Check the status of an Intellimatch search job | | **List contacts** `findymail_list_contacts` | Retrieve contacts from a specified list (paginated) | | **List excluded domains** `findymail_list_excluded_domains` | Retrieve domains excluded from Intellimatch searches | | **List exclusion lists** `findymail_list_exclusion_lists` | Retrieve all exclusion lists for managing excluded websites from Intellimatch searches | | **Search intellimatch** `findymail_search_intellimatch` | Find companies and contacts using natural language queries | | **Verify email** `findymail_verify_email` | Verify the deliverability of an email address | | **Add excluded domain** `findymail_add_excluded_domain` | Add domains to an exclusion list in Findymail | | **Create exclusion list** `findymail_create_exclusion_list` | Create a new exclusion list for Intellimatch searches | | **Create list** `findymail_create_list` | Create a new contact list | | **Update exclusion list** `findymail_update_exclusion_list` | Update an existing exclusion list | | **Update list** `findymail_update_list` | Update an existing contact list | | **Remove excluded domain** `findymail_remove_excluded_domain` | Remove domains from the exclusion list | ## Example prompts **Find Email By Name** > Use Findymail to find email by name and walk me through the result in plain English. **Get Contact Lists** > Pull the relevant data from Findymail, summarize it in plain English, and point out anything that needs attention. **Get Credits** > Pull the relevant data from Findymail, summarize it in plain English, and point out anything that needs attention. **Get Credits Summary** > Pull the relevant data from Findymail, 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 Findymail working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Findymail API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Findymail 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 Findymail. | 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 Findymail actions to the runtime in a format your agent can reliably use. | 21 tools for Findymail are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Findymail 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 Findymail in the browser, and the 21 tools above work from chat. There is no SDK and no config file, and the Findymail key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Findymail skill but can't call the tools The ClawHub skill teaches OpenClaw about Findymail, but the calls run through the ClawLink plugin and your connected account. Make sure Findymail 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 Findymail 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 Findymail tools Findymail 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 Findymail 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. ### Findymail 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 Findymail has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Findymail integration? Yes. ClawLink is the fastest way to connect OpenClaw to Findymail: link your Findymail account once in the browser and OpenClaw can call the Findymail API through 21 ready-made tools — no custom code or token handling. ### How do I add Findymail to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Findymail skill from ClawHub, then you click Connect in the dashboard to authorize Findymail. OpenClaw calls the tools from the next message — no config files, and the Findymail key you paste is stored server-side instead of in your environment. ### How long does it take to connect Findymail to OpenClaw? About two minutes. Sign in, click Connect next to Findymail in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Findymail 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 Findymail working from chat. ### OpenClaw installed the Findymail skill but can't call the tools The ClawHub skill teaches OpenClaw about Findymail, but the calls run through the ClawLink plugin and your connected account. Make sure Findymail 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 - [ActiveCampaign tools](https://claw-link.dev/openclaw/activecampaign) — Marketing automation, CRM, and email marketing - [Benchmark Email tools](https://claw-link.dev/openclaw/benchmark-email) — Benchmark Email is a comprehensive email marketing platform offering tools for creating, sending, and analyzing email campaigns. - [OpenClaw Mailchimp integration](https://claw-link.dev/openclaw/mailchimp) — Create email campaigns and manage audiences