How to connect Tomba to Hermes Agent
Connect Tomba to Hermes with ClawLink: paste your Tomba key once and 25 tools work from chat. No MCP server to run, nothing stored on your machine.

Tomba is an Email Finder for B2B sales and email marketing.. Once connected, Hermes Agent can read and act on Tomba from chat — pairing, token refresh, and tool wiring handled for you.
Most guides for giving Hermes Agent Tomba 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 Tomba setup: pair once in the browser and your always-on Hermes agent can act on Tomba 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 Tomba.
- 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
Connect Tomba
Paste your API key in the dashboard.
- 3
Use it from chat
Ask Hermes Agent: "What can you do with Tomba?"
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 testThen connect Tomba in the ClawLink dashboard — paste your Tomba API key once.
Verify the connection by asking Hermes:
Use Tomba to attributes list 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 loginlogin opens the same browser approval and stores a credential locally. Once Tomba is connected in the dashboard, that agent calls the same 25 Tomba tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Tomba MCP for Hermes
Looking for a Tomba MCP server for Hermes Agent? ClawLink connects Tomba to Hermes Agent and exposes 25 Tomba tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw Tomba integration works the same way.
What the Hermes Agent Tomba integration can do
25 Tomba tools are ready for Hermes Agent once the account is connected. The 23 below are the ones people reach for most; your agent can call all 25.
23 of 25 Tomba tools for Hermes
| Tool | What it does |
|---|---|
Attributes list tomba_attributes_list | Retrieves all custom lead attributes defined in your Tomba account |
Domain status tomba_domain_status | Check if a domain is webmail or disposable |
Enrich company tomba_enrich_company | Enrich one company from its domain; this does not look up a specific person |
Enrich person tomba_enrich_person | Enrich one person from an email address; use the company or combined actions for company-only |
Enrich person and company tomba_enrich_person_and_company | Enrich both a person and their company from one email in one request; use the focused actions |
Find author tomba_find_author | Find an article author's professional contact data from its URL |
Find email tomba_find_email | Find a professional email from company and person identifiers, optionally including an |
Find email from linkedin tomba_find_email_from_linkedin | Find the most likely professional email from a LinkedIn profile URL, optionally returning all |
Find phone tomba_find_phone | Find phone numbers by providing at least one of email, domain, or LinkedIn URL |
Get email count tomba_get_email_count | Return contact counts and department breakdown for a domain |
Get email format tomba_get_email_format | Return detected email patterns for a domain |
Get email sources tomba_get_email_sources | Return public web sources where an email address was found |
Get employee locations tomba_get_employee_locations | Return employee counts by country for a domain |
Keys list tomba_keys_list | List all API keys |
Leads list tomba_leads_list | List all leads |
Lists list tomba_lists_list | List all lead lists |
Search domain contacts tomba_search_domain_contacts | Search a domain or company for professional contacts, optionally including mobile phone |
Usage stats tomba_usage_stats | Get API usage statistics |
Validate phone tomba_validate_phone | Validate and format a phone number |
Verify email tomba_verify_email | Verify email deliverability and mailbox signals, optionally returning an associated mobile |
Leads create tomba_leads_create | Create a new lead in Tomba's lead database |
Lists update tomba_lists_update | Update a leads list's name by ID |
Verify emails tomba_verify_emails | Verify up to 1000 emails by managing Tomba's asynchronous bulk job synchronously |
Try it: find the Tomba tool you need
Browse the 23 Tomba tools
Click any tool to see exactly what Hermes can do and copy a ready-to-use prompt.
Example prompts
Use Tomba to attributes list 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 Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Tomba working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Tomba API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Tomba 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 Tomba. | 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 Tomba actions to the runtime in a format your agent can reliably use. | 25 tools for Tomba are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Tomba 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 Tomba in the browser, and the 25 tools above work from chat. There is no SDK and no config file, and the Tomba 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 Tomba
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 Tomba 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 Tomba tools
Tomba 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 Tomba 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.
Tomba 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 Tomba 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 Tomba integration?
Yes. ClawLink is the fastest way to connect Hermes to Tomba: link your Tomba account once in the browser and Hermes Agent can call the Tomba API through 25 ready-made tools — no custom code or token handling.
How do I connect Tomba 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 Tomba in the dashboard and Hermes can use it from the next message — no config files, and the Tomba key you paste is stored server-side instead of in your environment.
How long does it take to connect Tomba to Hermes Agent?
About two minutes. Sign in, click Connect next to Tomba in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.
Why use ClawLink instead of wiring Tomba 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 Tomba working from chat.
Hermes paired but still can't use Tomba
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.