Copy page

Automation

n8n

The Tomba node, npm package n8n-nodes-tomba, adds 45 Tomba operations to n8n workflows. Tomba builds and maintains it; the source is at github.com/tomba-io/n8n-nodes-tomba and the listing at n8n.io/integrations/tomba.

Prerequisites

• A Tomba API key and secret. See Get your key and secret.
• n8n Cloud or a self-hosted n8n instance, and an owner or admin account on it to install the node.

Install and connect

Install the node in one of two ways:

• From the nodes panel (n8n Cloud and self-hosted). Open the nodes panel, search for Tomba, select the node under More from the community, and select Install. n8n verifies the node, so it's available wherever verified community nodes are enabled; on n8n Cloud, an owner enables them in the Cloud Admin Panel.
• By package name (self-hosted only). Go to Settings > Community Nodes, select Install, enter n8n-nodes-tomba, accept the risk notice, and select Install.

Either way, the node is installed once for the whole instance.

Then connect your account:

1. Open the Tomba node and leave Authentication set to API Key.
2. Under Credential to connect with, create a Tomba API credential with your API Key and API Secret. n8n tests the credential with GET /v1/me.

The OAuth2 option needs an OAuth client ID and secret issued by Tomba. Use API Key unless Tomba has issued you a client.

Actions

Pick a Resource, then an Operation. Each operation sends one request, so it's charged and throttled like a direct API call: see Credit costs and Rate limits.

Operation details that differ from the API:

• Domain Search offers a Limit of 10, 20, or 50. Return All sends one request with limit=100, which is charged for 100 results (see Credit costs) and fails on the Free plan. Only Emails is on by default and returns only the addresses; turn it off to get the company data too.
• Email Finder needs Domain or Company, plus Full Name or both First Name and Last Name. The node doesn't mark these fields as required, so a request without them fails at the API with 422.
• Phone Finder searches by one of email, domain, or LinkedIn URL, chosen in Search Type.
• Lead > Create requires Email and List ID in the node. The API itself requires only the email.
• Email Finder, Email Verifier, Email Enrichment, Phone Finder, LinkedIn Finder, Author Finder, Domain Search, and Search Companies accept a Webhook URL. The node still waits for the response; see Per-request callbacks for which endpoints send a callback.

The node waits up to 120 seconds for each response.

For an endpoint the node doesn't cover, use the HTTP Request node: set Authentication to Predefined Credential Type, choose Tomba API, and select your credential. n8n adds the X-Tomba-Key and X-Tomba-Secret headers.

Example

Find an address for each incoming contact and keep only deliverable ones:

1. Trigger: a node that outputs first_name, last_name, and domain, such as a form or a spreadsheet row.
2. Tomba > Email > Email Finder: set Domain to {{ $json.domain }}, First Name to {{ $json.first_name }}, and Last Name to {{ $json.last_name }}. The output has the address in email.
3. Tomba > Email > Email Verifier: set Email to {{ $json.email }}. The output has the verification fields under email.
4. If: continue when {{ $json.email.result }} equals deliverable. Email verifier attributes lists the other values.

Troubleshooting