ClawLink

How to connect Tomba to OpenClaw

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

Get started for free
OpenClaw
OpenClaw
ClawLink
ClawLink
Tomba
Tomba
TombaAPI KEYMCP

Tomba is an Email Finder for B2B sales and email marketing.. Once connected, OpenClaw can read and act on Tomba from chat — pairing, token refresh, and tool wiring handled for you.

25 tools

The usual route to Tomba 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 Tomba setup: install one ClawHub skill, connect Tomba in the browser, and OpenClaw can call real Tomba 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 Tomba.

  1. 1

    Install 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. 2

    Connect Tomba

    Paste your API key in the dashboard.

  3. 3

    Use it from chat

    Ask OpenClaw: "What can you do with Tomba?"

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-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 Tomba in the ClawLink dashboard — paste your Tomba API key once.

Verify the connection by asking OpenClaw:

Use Tomba to attributes list 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 login

login 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 OpenClaw

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

What the OpenClaw Tomba integration can do

25 Tomba tools are ready for OpenClaw 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 OpenClaw

ToolWhat it does
Attributes list tomba_attributes_listRetrieves all custom lead attributes defined in your Tomba account
Domain status tomba_domain_statusCheck if a domain is webmail or disposable
Enrich company tomba_enrich_companyEnrich one company from its domain; this does not look up a specific person
Enrich person tomba_enrich_personEnrich one person from an email address; use the company or combined actions for company-only
Enrich person and company tomba_enrich_person_and_companyEnrich both a person and their company from one email in one request; use the focused actions
Find author tomba_find_authorFind an article author's professional contact data from its URL
Find email tomba_find_emailFind a professional email from company and person identifiers, optionally including an
Find email from linkedin tomba_find_email_from_linkedinFind the most likely professional email from a LinkedIn profile URL, optionally returning all
Find phone tomba_find_phoneFind phone numbers by providing at least one of email, domain, or LinkedIn URL
Get email count tomba_get_email_countReturn contact counts and department breakdown for a domain
Get email format tomba_get_email_formatReturn detected email patterns for a domain
Get email sources tomba_get_email_sourcesReturn public web sources where an email address was found
Get employee locations tomba_get_employee_locationsReturn employee counts by country for a domain
Keys list tomba_keys_listList all API keys
Leads list tomba_leads_listList all leads
Lists list tomba_lists_listList all lead lists
Search domain contacts tomba_search_domain_contactsSearch a domain or company for professional contacts, optionally including mobile phone
Usage stats tomba_usage_statsGet API usage statistics
Validate phone tomba_validate_phoneValidate and format a phone number
Verify email tomba_verify_emailVerify email deliverability and mailbox signals, optionally returning an associated mobile
Leads create tomba_leads_createCreate a new lead in Tomba's lead database
Lists update tomba_lists_updateUpdate a leads list's name by ID
Verify emails tomba_verify_emailsVerify 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 OpenClaw 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.

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 Tomba working from chat.

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

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 OpenClaw 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

OpenClaw installed the Tomba skill but can't call the tools

The ClawHub skill teaches OpenClaw about Tomba, but the calls run through the ClawLink plugin and your connected account. Make sure Tomba 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 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 OpenClaw Tomba integration?

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

How do I add Tomba to OpenClaw with ClawLink?

Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Tomba skill from ClawHub, then you click Connect in the dashboard to authorize Tomba. OpenClaw calls the tools 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 OpenClaw?

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

OpenClaw installed the Tomba skill but can't call the tools

The ClawHub skill teaches OpenClaw about Tomba, but the calls run through the ClawLink plugin and your connected account. Make sure Tomba 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.

On this page