Skip to main content

n8n integration

Add the Tomba node to n8n to find and verify emails automatically in your workflows.

Written by Tomba.io Team

Use n8n to run Tomba automatically as part of a workflow, which is a set of steps that runs on its own. For example, when a new contact arrives, n8n can find their email and check it.

n8n is a separate workflow tool. You can use n8n Cloud, or run it on your own server. Tomba builds and maintains the Tomba node. A node is one step in an n8n workflow.

Before you start

  • You need an n8n account. You must be an owner or admin on it to install the Tomba node.

  • You need your Tomba API key and secret. These are two private codes that let another app use your Tomba account.

Connect Tomba to n8n

You do this in n8n, not in Tomba. The N8n card on the Integrations page only opens a technical setup guide, so you can skip it.

The Automation group on the Integrations page, with the Zapier, Make, N8n and Apify names outlined

Step 1. In Tomba, open API in the left menu and copy your key and secret. For help, see How to find my API key?.

The API Keys page with an arrow on the API Key & Secret column, where each blurred value has a show and a copy button

Step 2. In n8n, open a workflow and open the nodes panel. Search for Tomba, select the node under More from the community, then select Install. You only do this once for your whole n8n account.

Step 3. Open the Tomba node and leave Authentication set to API Key.

Step 4. Under Credential to connect with, create a Tomba API credential. A credential is how n8n stores your login for an app. Enter your API Key and API Secret.

Step 5. Pick a Resource, then an Operation. For example, pick Email, then Email Finder.

Step 6. Link the node to the other steps in your workflow, test it, then turn the workflow on.

💡 Tip: If you run n8n on your own server, you can also install the node from Settings > Community Nodes. Enter n8n-nodes-tomba as the package name.

What Tomba can do in n8n

There's one Tomba node, with 45 operations, which are the jobs it can do. They're grouped by resource:

Resource

Operations

Domain

Domain Search, Domain Status, Autocomplete, Location, Similar, Technology

Email

Email Finder, Email Verifier, Email Enrichment, Email Count, Email Sources, Email Format

Finder

Author Finder, LinkedIn Finder

Phone

Phone Finder, Phone Validator

Company

Search Companies

Enrichment

Person, Company, Combined

Lead, Lead List, Lead Attribute

List, Get, Create, Update, Delete

Key

List, Get, Create, Reset, Delete

Account

Account, Usage, Logs

Flag

List, Create

Example: find and check a new contact

  1. Start: use a form or a spreadsheet row with a first name, last name and company website.

  2. Tomba > Email > Email Finder: fill in Domain, First Name and Last Name from step 1.

  3. Tomba > Email > Email Verifier: set Email to the email from step 2.

  4. If: continue only when the result is deliverable, which means mail should reach that email.

💳 Credits: Each operation costs the same as doing that search in Tomba. In this example, each contact uses 1 search credit when an email is found, and 1 verification credit to check it.

⚠️ Important: In Domain Search, Return All is charged as 100 results, which is 10 search credits. It also fails on the Free plan. To spend less, set Limit to 10, 20 or 50 instead.

Common questions

Why can't I find Tomba in the nodes panel?

Your n8n may have verified community nodes turned off. That's the group Tomba's node belongs to. On n8n Cloud, an owner turns them on in the Cloud Admin Panel. You also need to be an owner or admin to install a node.

Why did the credential test fail?

Your key or secret is wrong, or the key has expired. Every key has an expiry date. Copy both again from API Keys, and create a new key if yours has expired.

Why did Email Finder stop with an error?

A field is probably empty. n8n doesn't mark these as required, but Email Finder needs them: Domain or Company, plus Full Name or both First Name and Last Name.

Why is my new lead missing from its list?

This is a known problem with Lead > Create: the lead can arrive with no name and outside its list. Add the lead to the list yourself in Leads.

For developers: see the Tomba docs.

Related articles

Did this answer your question?