GetEmail.io
Sales IntelligenceFind and verify professional email addresses with GetEmail.io, using asynchronous lookups from a name plus domain. Agents resolve a contact before the outreach step spends a send on a guess.
What This Integration Enables
GetEmail.io has a deliberately small surface, and the interesting thing about it is what the API gives back rather than how much it does. A completed search returns email_search_details, which grades the candidate addresses it considered under good_email and bad_email, each carrying MX and machine learning check outcomes and scores. Most finders return a single address and a confidence number, which is the same reasoning with the working hidden. Getting the candidate set means an agent can tell the difference between an address that won decisively and one that edged out two near-identical alternatives, and those two situations deserve different treatment even though they look the same in a CRM field.
The second thing to build around is the asynchronous contract, which applies to both operations and applies differently to each. Find Email returns a record with an id and an is_terminated flag; when the flag is false, the agent polls Get Find Email Status with that id until the search completes. Verification has no separate result endpoint at all, so if Verify Email comes back with is_terminated false, the correct move is to wait and call the same action again with the identical address. FlowRunner's intelligent waiting handles both shapes without a developer writing a retry loop. Include Enrichment adds a block with job title, industry, location, social profiles and company history alongside the address, which turns a lookup into a usable contact record in one pass. One constraint is worth designing around openly: GetEmail.io publishes no credit balance endpoint, so an agent cannot ask what is left before it starts. Spend has to be governed by batch size and by a person, not by a pre-flight check.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Backfilling an imported list
A list import lands in HubSpot with names and companies and a large hole where the email addresses should be. The agent works the list one record at a time, calling Find Email with Include Enrichment, polling Get Find Email Status until the search terminates, then writing back the address together with the job title, industry and location from the enrich_data block. Records that resolved cleanly are marked ready. Records that terminated without a result are marked as needing a different source rather than left blank, which is the difference between a queue somebody can work and a field that looks like an oversight.
Verification as an import gate
Addresses arriving from a partner list, a webinar registration or a form are routed through Verify Email before they touch the CRM. Because verification has no result endpoint, the agent handles is_terminated false by waiting and calling the same action again with the identical address, rather than treating an incomplete check as a failure. Addresses that verify are created as contacts. Addresses that do not are written to a review sheet in Google Sheets with the verification status and the algorithm used, so whoever supplied the list can see which parts of it were unusable.
A finder-first enrichment step for a small team
A two-person outbound team does not want a database subscription and a separate enrichment tool. The agent uses Find Email with Include Enrichment as the single step between a name and a workable record, pulling title, industry, location, social profiles and company history at the same time as the address. The output goes to Airtable as the working prospect list. It is a narrow connector doing one job properly, which is often the right shape when the alternative is paying for a platform to solve a lookup.
Human-in-Loop Highlight
The failure mode that matters here is not a bounce. It is a guess that arrives dressed as a fact. GetEmail.io evaluates several candidate addresses and returns them graded, so when the winning candidate scores close to a runner-up the API is effectively telling you it picked one of two plausible people, or one of two plausible patterns at the same company. Mail it and the worst case is not a bounce at all, it is a real message reaching a real person who is not the one you meant. There is also no credit balance endpoint to lean on, so a flow cannot silently absorb the cost of retrying its way out. The agent therefore holds the marginal cases: "Find Email for [Name] at [Domain] terminated with [address] as the top candidate. Runner-up [address] scored within [margin], and the MX check on the winner returned [result]. Send as verified, hold for a second source, or discard?" The reviewer sees the same evidence the API produced and decides. This is what a digital andon cord is for. The clear-cut results flow through untouched, and the line stops only where the data itself was not clear-cut.
Agent Capabilities
3 actionsEmail Finding
2- Find Email Starts a search for a person's professional email from their full name and company domain, returning a search record with an id plus is_terminated and is_success flags. The search runs asynchronously, so when is_terminated is false, poll Get Find Email Status with the returned id. Include Enrichment adds an enrich_data block with job title, industry, location, social profiles and current and previous companies.
- Get Find Email Status Retrieves the current state of a previously started search using the id returned by Find Email. The response has the same shape as Find Email, so poll until is_terminated is true and then read the email and email_search_details fields. An unrecognised id returns an ERROR_THIS_ID_NOT_EXIST error.
Verification
1- Verify Email Checks whether an email address is deliverable, returning a verification status, the algorithm used and the time the check took. Verification is asynchronous and has no separate result endpoint, so if is_terminated comes back false, wait briefly and call this action again with the identical address to collect the finished result.
Frequently Asked Questions
What can FlowRunner do with GetEmail.io?
FlowRunner agents can run Find Email, Get Find Email Status, and Verify Email in GetEmail.io.
Does connecting GetEmail.io to FlowRunner require OAuth?
No. GetEmail.io connects to FlowRunner with an API key, no OAuth flow required.
Can GetEmail.io trigger a FlowRunner workflow automatically?
GetEmail.io doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with GetEmail.io
$100 in credits. No card required. Connect in minutes.