Skip to content

Power Automate Email Finder: Build a Lead Flow Step by Step

Build a Power Automate email finder flow that takes a name and domain, calls the Tomba API, and writes the result back to your list.

Nov 16, 2026 5 min read 1,131 words
Power Automate Email Finder: Build a Lead Flow Step by Step
Power Automate email finder: build a lead flow step by step
Power Automate email finder: build a lead flow step by step

A Power Automate email finder flow saves the copy-and-paste work that eats a prospecting day. You add a name and a company domain to a list. The flow looks up the email address, checks it, and writes the result back. Nobody opens another tab.

This guide builds that flow step by step. It uses Power Automate's HTTP action to call the Tomba API, so it works today. Tomba is also preparing a native connector, and we cover where that stands below.

What you need before you start#

  • A Microsoft account with access to Power Automate.
  • A list to work from, such as an Excel table on OneDrive, a SharePoint list or Dataverse. This guide uses an Excel table with the columns FirstName, LastName, Domain, Email and Status.
  • A Tomba API key and secret, available in your account at app.tomba.io. If you are new, create an account first.

A note on licensing: the HTTP action may need a premium Power Automate plan, depending on your license. Check your plan before you build.

How the Power Automate email finder flow works#

The flow follows four steps:

  1. A row appears in your list.
  2. The flow sends the name and domain to Tomba's email finder.
  3. If an address comes back, the flow verifies it.
  4. The flow writes the email and a status back to the row.

Keep the logic of your Power Automate email finder small. A short flow is easier to debug and cheaper to run.

Step 1: Choose the trigger#

Pick a trigger that fits where your leads live. Common choices:

  • When a row is added to a table for Excel Online.
  • When an item is created for SharePoint.
  • Recurrence to process a batch every night.

For a first test, use a manual button trigger and loop over a short list. It lets you watch each run.

Step 2: Call the Tomba email finder#

Add an HTTP action with these settings:

  • Method: GET
  • URI: https://api.tomba.io/v1/email-finder?domain=@{triggerBody()?['Domain']}&first_name=@{triggerBody()?['FirstName']}&last_name=@{triggerBody()?['LastName']}
  • Headers: X-Tomba-Key and X-Tomba-Secret, set to your key and secret

The API reference lists the same endpoint. A domain gives better results than a company name. If no name can be read from the request, the API answers with a 422 error, so make sure both name fields are filled.

Store the key and secret as secure inputs or in an environment variable, never in plain text in a shared flow.

Step 3: Parse the response#

Add a Parse JSON action on the body of the HTTP step. You only need a small schema:

{
  "type": "object",
  "properties": {
    "data": {
      "type": "object",
      "properties": {
        "email": { "type": ["string", "null"] },
        "score": { "type": ["number", "null"] }
      }
    }
  }
}

The API returns data.email, which is null when no address is found, and the response is still a normal 200. That matters. A "success" status does not mean you got an address, so test the value, not the status code.

Step 4: Handle an empty result#

Add a Condition action: is data.email empty?

  • Yes: update the row with Status = Not found. Stop there.
  • No: continue to verification.

Without this branch, a missing address breaks the next step and your flow shows as failed for a normal case.

Step 5: Verify the address#

Finding an address and confirming it works are separate jobs. Add a second HTTP action that calls the verification endpoint with the address you found. Tomba's email verifier checks the domain, the server and the mailbox. Then branch again:

  • Deliverable: write Status = Verified.
  • Risky or unknown: write Status = Review, so a person can decide.
  • Undeliverable: write Status = Invalid and leave the email column empty.

Credits for finding and verifying are separate balances on Tomba, so plan both when you size a batch.

Step 6: Write the result back#

Add an Update a row action (Excel) or Update item action (SharePoint). Map Email to data.email and Status to the value from your branch. Add a timestamp column if you want to know when each lookup ran.

Common Power Automate email finder problems#

Symptom Likely cause Fix
Flow fails with a 401 Wrong key or secret Re-copy both from your Tomba account
Flow fails with a 422 Missing first or last name Add a condition that skips rows without a name
Email column stays empty The lookup found nothing Check the Not found rows by hand
Flow runs many times on one row The update re-triggers the flow Add a condition on the Status column
A big batch stalls Throttling Add a short delay or lower the concurrency

The re-trigger loop is the classic mistake. When your flow updates the same table that starts it, add a condition at the top so rows with a status are skipped.

What about a native Tomba connector?#

A native Power Automate email finder connector would remove the HTTP setup. Tomba's Power Automate page describes a connector with actions for finding, verifying and enriching contacts. As of this writing, that page says the connector is not yet available and must pass Microsoft's certification before it appears in the connector list. Until then, the HTTP approach in this guide is the way to go. Check the page for updates.

Tips for a Power Automate email finder you can trust#

  • Test on five rows first. Read each result before you scale up.
  • Log failures. Write the error text to a column so you can see patterns.
  • Respect privacy rules. Only process data you have a lawful reason to use, and keep your retention short.
  • Keep one source of truth. Sync the final list to your CRM through Tomba integrations or your own flow.

FAQ#

Can Power Automate find email addresses?#

Not by itself. It connects services. To find an address you call a finder, such as the Tomba API, from a flow step.

Do I need to code to build a Power Automate email finder?#

No. The HTTP, Parse JSON and Condition actions are all configured with forms and expressions.

What if the lookup returns no email?#

Treat it as a normal result. Mark the row Not found and move on. Not every person can be matched to an address.

How do I keep my API key safe?#

Use secure inputs or an environment variable. Do not paste keys into a flow that many people can edit.

Can my Power Automate email finder run on a whole file at once?#

You can loop over many rows, but large jobs run better as a batch. For a one-off file, Tomba's bulk tasks take a CSV and do the lookups for you.

// start free

See who Tomba finds at any company

Type a company's domain to see its people, their roles and verified work emails, each with the pages it was found on. Free account, no card.

Free plan · No credit card required · GDPR & CCPA

Share
0 clapsEnjoyed it? Give a clap.
AU

// about the author

Tomba Editorial Team

Was this helpful?