// power automate connector · coming soon
Tomba for Power Automate
Find, verify and enrich contacts as steps in your flows. The connector adds 26 Tomba actions to Power Automate, Power Apps, Logic Apps and Copilot Studio.
// 01 · in the connector
Every action, ready for your flows
26 actions for finding, verifying and enriching contacts. Add one as a step, give it your inputs, and use what it returns in the steps after it.
Every email at a company, in one step
Send a domain or a company name. The action returns the organization and the addresses Tomba has for it, for your next step to use.
Names in, an address out
Send a first and last name, or a full name, with a domain or a company. The action returns the address with its score. When there's no match, the step still succeeds and the email is empty.
Check an address before you send
Send an address to see whether it can receive mail, with the outcome and each individual check in the response. It uses verification credits, not search credits.
A phone number for each contact
Start from an email address, a domain or a LinkedIn profile, and get the formats, line type and carrier. When nothing is found, data is an empty array, so test it before you read its fields.
The person behind each address
Send an address to get the person and the company behind it. Enrich person, Enrich company and Enrich person and company do the same from other starting points.
Build company lists in one step
Describe your market in a sentence, set filters, or both. The action searches Tomba's company database and returns the companies for your next step.
See the tech stack behind a website
Send a domain to list the technologies its website uses, by category. Find similar companies turns one customer into a lookalike list the same way.
// 02 · in your flow
26 actions, each one an API call
Each action calls one Tomba endpoint with your connection and costs what that endpoint costs. A flow that succeeds can still mean Tomba found nothing, so check the result before you use it.
- 200 with a result
- The fields are filled in and ready for the next step.
- 200 with no result
- The step succeeds, but the email is empty, errors is set or data is an empty array. Check for it in your flow.
- 400, 401, 422 or 429
- The step fails. Add a step that runs after the failure to handle a bad input, bad credentials or a rate limit.
| Action | Endpoint | Cost |
|---|---|---|
| // Find email | ||
| Search domain | GET/domain-search | 1 search credit per 10 results |
| Find email address | GET/email-finder | 1 search credit |
| Find article author | GET/author-finder | 1 search credit |
| Find email from LinkedIn profile | GET/linkedin | 1 search credit |
| Get email count | GET/email-count | 1 email count credit |
| Get email format | GET/email-format | 1 email count credit |
| Get email sources | GET/email-sources | 1 email sources credit |
| // Verify | ||
| Verify email address | GET/email-verifier | 1 verification credit |
| Get domain status | GET/domain-status | Free |
| // Enrich | ||
| Enrich email address | GET/enrich | 1 search credit |
| Enrich person | GET/people/find | 1 search credit |
| Enrich company | GET/companies/find | 1 search credit |
| Enrich person and company | GET/combined/find | 2 search credits |
| // Phone | ||
| Find phone number | GET/phone-finder | 5 search credits |
| Validate phone number | GET/phone-validator | 1 search credit |
| // Companies | ||
| Search companies | POST/reveal/search | 1 search credit |
| Find similar companies | GET/similar | 1 search credit per 10 results |
| Get website technologies | GET/technology | Free |
| Suggest companies | GET/domain-suggestions | |
| Get employee locations | GET/location | 1 email count credit |
| // Account | ||
| Get API usage | GET/usage | |
| Get request logs | GET/logs | |
| // Leads and flags | ||
| List leads | GET/leads | |
| Create lead | POST/leads | Free |
| List flags | GET/flag | |
| Flag incorrect data | POST/flag | |
// 03 · whole lists
A step for every row, inside your flow
Put a Tomba action inside Apply to each to run it on every row of a list, then write the answer back. The flow does the looping, so plan for the limits below.
- Rate limits are shared
- Every key and connection on your account counts toward the same limits, which depend on your plan. A request over a limit fails with status 429.
- Long requests can time out
- Tomba recommends a client timeout of at least 180 seconds, and Power Automate stops synchronous requests at 120. For large volumes, use bulk jobs in the Tomba dashboard.
- Each row uses credits
- Most lookups cost credits, and Enrich Mobile costs extra. Check your balance with Get API usage before a long run.
// 04 · setup
Set up the connector in minutes
- 01
Add a Tomba action
In a flow, search for Tomba and pick an action.
- 02
Create a connection
Enter your API key and API secret from app.tomba.io/api.
- 03
Give it your inputs
Type a value, or use one from an earlier step.
- 04
Use the result
Pick the action's outputs in the steps after it.
// 05 · use it anywhere
The same endpoints beyond your flows
One account, one set of credits: the API, bulk jobs, the browser extension and AI agents call the same endpoints.
- REST APIJSON over HTTPS, 13 SDKs, signed webhooks.
GET /v1/email-finder - Bulk CSVUpload a list in the app or POST it to /bulk; download when it's done.
POST /v1/bulk/{type} - MCP for AI agentsRemote MCP server, 28 tools, OAuth sign-in.
https://mcp.tomba.io/mcp - Browser extensionEmails on LinkedIn and on any website you visit.
Chrome · Edge · Firefox · Safari