Automation
Make
The Tomba Email Finder app adds 12 Tomba modules to Make scenarios. Make lists it as a verified app from the official vendor at make.com/en/integrations/tomba.
Prerequisites
- A Tomba API key and secret. See Get your key and secret.
- A Make account.
Install and connect
- In a scenario, add a module and search for Tomba Email Finder.
- Choose a module from the table below.
- Create a connection with your API Key and Secret key.
The app has no triggers. Start the scenario with another app's module, a webhook, or a schedule.
Actions
Each module sends one request, so it's charged and throttled like a direct API call: see Credit costs and Rate limits.
| Module | Type | Endpoint |
|---|---|---|
| Search email address | Search | GET /email-finder |
| Email verifier | Search | GET /email-verifier |
| Search domain emails | Search | GET /domain-search |
| Search email | Search | GET /enrich |
| Search author | Search | GET /author-finder |
| Search LinkedIn email | Search | GET /linkedin |
| Search phone | Search | GET /phone-finder |
| Phone validator | Search | GET /phone-validator |
| Search similar domains | Search | GET /similar |
| Search emails | Search | GET /email-count |
| Create a lead | Action | POST /leads |
| Make an API Call | Action | Any Tomba endpoint, using the connection's credentials |
Parameter rules come from the API:
- Search domain emails: the API reference documents a
limitof 10, 20, or 50. On the Free plan, a limit above 10 fails; see Free plan limits. - Search email enriches an email address only. To look up a company by domain, call
GET /companies/findwith Make an API Call. - Search emails returns the number of addresses for a domain, not the addresses.
Example
Find and verify an address for each new spreadsheet row, and add deliverable addresses to your CRM:
- Google Sheets: a module that watches for new rows in a sheet with first name, last name, and company domain columns.
- Tomba Email Finder, Search email address: map the name and domain columns.
- Tomba Email Finder, Email verifier: map the address from step 2.
- Filter: continue only when the verifier's
resultisdeliverable. Result values lists the other values. - Your CRM: create the contact.
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
| The connection fails | The key or secret is wrong or malformed, or the key has expired. | Copy both values again from API keys. Replace an expired key; see Key expiry. |
A module fails with 402 | Not enough credits for the request. | See Credits and usage. |
A module fails with 429 | A rate limit was hit, or the email count balance is used up. | Process fewer bundles per run, or add an error handler that retries later. See Handle 429 responses. |
A module fails with 451 | The address, profile, or phone number is withheld at its owner's request. | Remove the record from your data. |
A module fails with 422 | A parameter is missing or has an invalid value. | Check the parameter in the API reference. Errors lists every error type. |
Last modified on