Resources · Make integration

Tomba Email Finder Make integrationAutomate Tomba Email Finder with Make.

Need a verified work email for every new prospect without copying names into Tomba by hand? The Tomba Email Finder Make integration gives you 12 modules: 10 searches and 2 actions. This guide is for sales and growth teams, and it walks you from the connection to a first working scenario.

Try the Tomba Email Finder integration on MakeSee the 12 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Tomba Email Finder Make integration do?

The Tomba Email Finder Make integration lets a Make scenario (the automation you build in Make, a chain of steps) ask Tomba for emails, phone numbers and company data, then pass the answer to your other tools. Each step is a module, one brick of the scenario, and Tomba brings 12 of them.

A clean email for each new contact. A prospect lands in your CRM with a name and a company website. Search email address looks for the professional address, and Email verifier checks it before anyone writes to it.

A full picture of a target account. Give Search domain emails a company domain and it returns the addresses Tomba knows for it. Pair it with Search emails first if you only want the count, or with Search similar domains to find lookalike companies worth prospecting.

Richer records from what you already have. An email with no context? Search email adds person and company data. A LinkedIn profile URL or a blog article? Search LinkedIn email and Search author turn them into an address. Before you judge Make itself, the Make review and the Make pricing page are worth a look.

What the integration does not do: Tomba has no trigger module, so it never starts a scenario by itself. The first step always comes from another app or from a schedule. Also note that the Make documentation for this app is flagged as AI-generated, so check important details with Tomba. Many apps also exist as an n8n node; the n8n vs Make comparison lays out the criteria.

Connect

How do you connect Tomba Email Finder to Make?

  1. 01

    Copy your two keys from Tomba

    You need an active Tomba account. In Tomba, open the API section of your account and copy both the API key and the Secret key shown on screen. Keep them at hand for the next step.

  2. 02

    Add a Tomba module and create the connection

    In your Make scenario, add any Tomba Email Finder module and click Create a connection. A connection is your Tomba account linked to Make once, then reused by all 12 modules. The Connection name field is optional.

  3. 03

    Paste the keys and save

    Paste the API key and the Secret key into the matching fields, or follow the instructions Make shows on screen, then save. The module can now talk to your Tomba account.

First scenario

Your first scenario with Tomba Email Finder

GoalWhen a new prospect appears in another app, Make finds the work email with Tomba Email Finder and checks that it is valid.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. Pick the app where your prospects live, the one that holds their name and company domain, as the first module.

  2. 02

    Add Search email address

    Click the + to the right of the first module, search for Tomba Email Finder and choose Search email address. Map the person's name and the company domain from the previous module.

  3. 03

    Check the result with Email verifier

    Add Email verifier after it and map the email found in the previous step. You now know whether the address is worth using before it reaches your outreach tool.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles, the items passed from module to module. A search can return no bundle at all, so test with a real prospect.

  5. 05

    Schedule it and switch it on

    Open the clock on the first module to set the schedule (every 15 minutes by default), then switch the scenario on. Every module run counts as an operation on your Make plan.

Modules

What can Tomba Email Finder do in Make?

Tomba Email Finder gives you 12 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Tomba Email Finder1

Create a lead

Action

In Make“Create a new lead . If the email already exists, fails with 422 status code.”

Saves a new lead in your Tomba account, so the contacts your scenario finds end up in one place on the Tomba side too.

When to use it
at the end of a prospecting flow, once an address has been found and checked, to keep Tomba as your list of record.
Watch out
if the email already exists in Tomba, the module fails with a 422 status code, so add an error route or filter known contacts first.
Tomba Email Finder2

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Lets you call any endpoint of the Tomba API from your scenario, using the same connection as the other modules, which covers what the ready-made modules leave out.

When to use it
when Tomba offers something in its API that none of the listed modules covers.
Watch out
you build the request yourself, so keep the Tomba API documentation open while you write it.
Tomba Email Finder3

Email verifier

Search

In Make“Verifies email addresses.”

Tells you whether an email address is deliverable before you use it, so fewer messages in your campaigns bounce back.

When to use it
right after any module that finds an address, or on an old list you are about to import into a mailing tool.
Watch out
it checks addresses, it does not find them; pair it with a search module when you start from a name.
Tomba Email Finder4

Phone validator

Search

In Make“Validates phone numbers and retrieves associated information.”

Checks that a phone number is valid and returns the information attached to it, so your sales team does not dial numbers that lead nowhere.

When to use it
when a form or a CRM hands you numbers typed by people, before they go into a calling list.
Watch out
it validates a number you already have; to find a number in the first place, use Search phone.
Tomba Email Finder5

Search author

Search

In Make“Retrieves the most likely email address from a blog post URL.”

Gives you the most likely email address of the person who wrote a blog post, starting from nothing more than the article URL.

When to use it
for link-building or PR outreach, when your list is a set of articles rather than a set of names.
Watch out
Tomba returns a likely address, not a certain one, so run it through Email verifier before sending anything.
Tomba Email Finder6

Search domain emails

Search

In Make“Searches for all email addresses associated with a domain.”

Returns all the email addresses Tomba links to a company domain, which is handy when you want to reach several people at one target account.

When to use it
for account-based prospecting, once a company is qualified and you need its contacts.
Watch out
it is a search, so it can send out many bundles, and each module after it runs once per bundle and counts operations.
Tomba Email Finder7

Search email

Search

In Make“Enrichment lets you look up person and company data based on an email.”

Turns a bare email address into a profile, adding what Tomba knows about the person and their company.

When to use it
when a newsletter signup or a demo request arrives with only an email and your sales team needs context before calling back.
Watch out
the name is close to Search emails and Search email address, so check the module you picked in the list: this one starts from an email.
Tomba Email Finder8

Search email address

Search

In Make“Find a professional email address using a person's name and company domain.”

Finds the professional email of a specific person from their name and their company domain. It is the module most prospecting scenarios start with.

When to use it
when a new prospect arrives from a form, a spreadsheet or your CRM with a name and a website but no email.
Watch out
a search can return nothing, so add a filter after it to stop the flow when no address came back.
Tomba Email Finder9

Search emails

Search

In Make“Lists the number of email addresses for a domain.”

Tells you how many email addresses Tomba holds for a domain, without returning the addresses themselves.

When to use it
as a quick check before Search domain emails, to skip companies where Tomba has little to offer and save operations further down.
Watch out
you get a number, not contacts, so map it into a filter rather than into your CRM.
Tomba Email Finder10

Search LinkedIn email

Search

In Make“Find email address from a LinkedIn profile url.”

Finds an email address from a LinkedIn profile URL, so a profile you spotted becomes someone you can actually write to.

When to use it
when your team collects LinkedIn profile links in a sheet or a CRM field and wants the matching emails without doing each lookup by hand.
Watch out
feed it the profile URL itself, not a name, and verify what comes back before an email campaign.
Tomba Email Finder11

Search phone

Search

In Make“Searches for phone numbers.”

Looks up phone numbers in Tomba, which gives your sales team a second way to reach a prospect when email alone stays unanswered.

When to use it
for high-value accounts where a call is worth the effort after the email sequence.
Watch out
like any search, it may return zero or several numbers, so decide in the next module which one you keep.
Tomba Email Finder12

Search similar domains

Search

In Make“Searches for similar domains based on a specific domain.”

Suggests companies whose domain is similar to one you give it, a simple way to grow a target list from an account you already like.

When to use it
after a deal closes, to find lookalike companies and feed them into Search domain emails.
Watch out
each suggested domain arrives as its own bundle, so every module you chain after it multiplies the operations used.
Need help

Need help automating Tomba Email Finder with Make?

A person reads every message.

FAQ

Questions about the Tomba Email Finder Make integration

01Is the Tomba Email Finder Make integration free?
Yes on the Make side: Tomba Email Finder is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) bring the interval down to 1 minute and count usage in credits each month. On the Tomba side, you need an active Tomba account and its API key; the subscription itself is described on the Tomba pricing page.
02What do you need to connect Tomba Email Finder to Make?
An active Tomba account and two values from its API section: the API key and the Secret key. In Make, add any Tomba Email Finder module, click Create a connection, give it a name if you like, and paste both keys. The connection is then shared by all 12 modules of the app, so you set it up once. Nothing to install on the Tomba side: the keys are all Make needs.
03Can Tomba Email Finder start a Make scenario on its own?
No. Tomba Email Finder has no trigger module in Make, neither scheduled nor instant, so it cannot launch a scenario by itself. You start the scenario with a module from another app, such as the CRM or form where new prospects appear, then place the Tomba modules after it. You can also run the scenario on a schedule set on the first module, every 15 minutes by default, and every 1 minute at the shortest on a paid plan.
04What if the Tomba Email Finder module you need is missing in Make?
Use Make an API Call. It sends any request to the Tomba API with the connection you already have, so whatever the API offers is reachable even without a dedicated module. You will need the Tomba API documentation to write the request. Keep in mind one known limit of the listed modules: Create a lead fails with a 422 status code when the email already exists in Tomba, so plan an error route or a filter for that case.
05Should you use Make or n8n for Tomba Email Finder?
It depends on the tool your team already runs. On Make, Tomba Email Finder comes with 12 ready modules plus Make an API Call, a visual editor and a Free plan to test with, which is enough to build a prospecting flow without code. Many apps also have an n8n node, so if your automations already live in n8n, check what that node covers before splitting your stack across two tools. The n8n vs Make comparison linked in this page walks through the criteria.
Same platform

Other docs you might need on this stack.

Browse all integrations