ClawLink

How to connect Findymail to Hermes Agent

Connect Findymail to Hermes with ClawLink: paste your Findymail key once and 21 tools work from chat. No MCP server to run, nothing stored on your machine.

Get started for free
Hermes Agent
Hermes Agent
ClawLink
ClawLink
Findymail
Findymail
FindymailAPI KEYMCP

Findymail is a B2B email and phone data provider offering verified contact information, email verification, automated exports, and CRM enrichment to enhance sales prospecting and outreach efforts.. Once connected, Hermes Agent can read and act on Findymail from chat — pairing, token refresh, and tool wiring handled for you.

21 tools

Most guides for giving Hermes Agent Findymail access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical Findymail setup: pair once in the browser and your always-on Hermes agent can act on Findymail for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself.

Setup

It takes three steps to connect Hermes to Findymail.

  1. 1

    Install and pair

    Install the ClawLink plugin, then pair Hermes with a one-time browser approval:

    hermes plugins install ClawLink-HQ/hermes-plugin --enable
  2. 2

    Connect Findymail

    Paste your API key in the dashboard.

  3. 3

    Use it from chat

    Ask Hermes Agent: "What can you do with Findymail?"

Install by command

The prompt above walks Hermes through this. By hand, it is four commands and a browser approval:

hermes plugins install ClawLink-HQ/hermes-plugin --enable
hermes clawlink begin    # prints an approval link — open it and approve
hermes clawlink finish   # after approving in the browser
hermes clawlink test

Then connect Findymail in the ClawLink dashboard — paste your Findymail API key once.

Verify the connection by asking Hermes:

Use Findymail to find email by name and walk me through the result in plain English.

Using a different agent?

The Hermes 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 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.

Findymail MCP for Hermes

Looking for a Findymail MCP server for Hermes Agent? ClawLink connects Findymail to Hermes Agent and exposes 21 Findymail tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw Findymail integration works the same way.

What the Hermes Agent Findymail integration can do

21 Findymail tools are ready for Hermes Agent 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 Hermes

ToolWhat it does
Find email by name findymail_find_email_by_nameFind someone's email using their full name and company domain
Get contact lists findymail_get_contact_listsRetrieve all contact lists
Get credits findymail_get_creditsCheck available API credits for your Findymail account
Get credits summary findymail_get_credits_summaryRetrieve credits usage summary report for the authenticated account
Get credits team summary findymail_get_credits_team_summaryRetrieve team credits usage summary report
Get exclusion list findymail_get_exclusion_listRetrieve a specific exclusion list by ID
Get intellimatch data findymail_get_intellimatch_dataRetrieve data from an Intellimatch search
Get intellimatch status findymail_get_intellimatch_statusCheck the status of an Intellimatch search job
List contacts findymail_list_contactsRetrieve contacts from a specified list (paginated)
List excluded domains findymail_list_excluded_domainsRetrieve domains excluded from Intellimatch searches
List exclusion lists findymail_list_exclusion_listsRetrieve all exclusion lists for managing excluded websites from Intellimatch searches
Search intellimatch findymail_search_intellimatchFind companies and contacts using natural language queries
Verify email findymail_verify_emailVerify the deliverability of an email address
Add excluded domain findymail_add_excluded_domainAdd domains to an exclusion list in Findymail
Create exclusion list findymail_create_exclusion_listCreate a new exclusion list for Intellimatch searches
Create list findymail_create_listCreate a new contact list
Update exclusion list findymail_update_exclusion_listUpdate an existing exclusion list
Update list findymail_update_listUpdate an existing contact list
Remove excluded domain findymail_remove_excluded_domainRemove domains from the exclusion list

Try it: find the Findymail tool you need

Browse the 19 Findymail tools

Click any tool to see exactly what Hermes can do and copy a ready-to-use prompt.

Example prompts

Use Findymail to find email by name and walk me through the result in plain English.

Pull the relevant data from Findymail, summarize it in plain English, and point out anything that needs attention.

Pull the relevant data from Findymail, summarize it in plain English, and point out anything that needs attention.

Pull the relevant data from Findymail, summarize it in plain English, and point out anything that needs attention.

The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Findymail working from chat.

ManualClawLink
Credential handlingCollect, 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 maintenanceYou 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 usabilityYou 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.

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 Hermes Agent 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 comparison.

Troubleshooting

Hermes paired but still can't use Findymail

Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.

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.

FAQ

Is there a Hermes Agent Findymail integration?

Yes. ClawLink is the fastest way to connect Hermes to Findymail: link your Findymail account once in the browser and Hermes Agent can call the Findymail API through 21 ready-made tools — no custom code or token handling.

How do I connect Findymail to Hermes with ClawLink?

Install the plugin with hermes plugins install ClawLink-HQ/hermes-plugin --enable, then pair once: run hermes clawlink begin, approve the link in your browser, and run hermes clawlink finish. Connect Findymail in the dashboard and Hermes can use it 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 Hermes Agent?

About two minutes. Sign in, click Connect next to Findymail in the dashboard, authenticate, and Hermes Agent 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 Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Findymail working from chat.

Hermes paired but still can't use Findymail

Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.