Automation
Zapier
Tomba's Zapier app adds 12 Tomba actions to your Zaps: 9 searches and 3 creates. Tomba builds and maintains the app; it's listed at zapier.com/apps/tomba.
Prerequisites
- A Tomba API key and secret. See Get your key and secret.
- A Zapier account.
Install and connect
- In the Zap editor, add an action step and search for Tomba. The app has no triggers, so start the Zap with another app's trigger, such as a new spreadsheet row or Webhooks by Zapier.
- Choose an action event from the table below.
- When Zapier asks for an account, enter your API KEY and Secret Key. Zapier tests the connection with
GET /v1/me.
Actions
Each action sends one request, so it's charged and throttled like a direct API call: see Credit costs and Rate limits.
| Action | Type | Endpoint | Inputs |
|---|---|---|---|
| Find Email | Search | GET /email-finder | domain and full name, both required |
| Email Verifier | Search | GET /email-verifier | Email, required |
| Domain Search | Search | GET /domain-search | Domain, required. Returns the first 10 addresses. |
| Email Enrichment | Search | GET /enrich | Email, required |
| Author Finder | Search | GET /author-finder | url, required |
| LinkedIn Finder | Search | GET /linkedin | LinkedIn URL, required |
| Phone Finder | Search | GET /phone-finder | Email, Domain, or LinkedIn URL. Zapier marks none as required; fill in at least one. |
| Phone Validator | Search | GET /phone-validator | Phone Number, required; Country Code, optional |
| Similar Domains | Search | GET /similar | Domain, required |
| Create Lead | Create | POST /leads | Email, required; First name and Last name, optional |
| Count Email | Create | GET /email-count | Domain, required |
| Domain Status | Create | GET /domain-status | Domain, required |
Count Email and Domain Status only read data, but Zapier lists them with the create actions.
Actions return the API response as is, so most fields appear under Data: for example, Data Email for Find Email and Data Email Result for Email Verifier. The response reference pages, such as Person and Email verifier attributes, describe the fields.
Example
Find and verify an address for each new spreadsheet row, and create a contact only when it's deliverable:
- Trigger: Google Sheets, New Spreadsheet Row, on a sheet with a full name column and a company domain column.
- Tomba, Find Email: map domain and full name from the row.
- Tomba, Email Verifier: map Email to Data Email from step 2.
- Filter by Zapier: continue only if Data Email Result exactly matches
deliverable. Result values lists the other values. - Your CRM: create the contact.
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
| Connecting the account 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. |
Step fails with 402 | Not enough credits for the request. | See Credits and usage. |
Step fails with 429 | A rate limit was hit, or the email count balance is used up. | Space the steps with Delay by Zapier. See Handle 429 responses. |
Step fails with 451 | The address, profile, or phone number is withheld at its owner's request. | Remove the record from your data. |
Phone Finder fails with 422 | None of Email, Domain, or LinkedIn URL was filled in. | Map at least one of them. |
| "The app did not respond in-time. It may or may not have completed successfully." | Zapier stops waiting for an action after 30 seconds, even if Tomba completes the request. | Run the step again. Repeating the same request in the same usage window isn't charged again; see Duplicate requests. |
| Tomba isn't offered as a trigger | The app provides actions only. | Start the Zap with another app's trigger. |
Last modified on