This feature requires one of the new GetSales plans (Send, Enrich, or Scale). If you're on a legacy plan, you'll need to upgrade to access this node and use the credits it consumes. See GetSales Pricing Plans for details.
The Find Email node automatically searches for a lead's work email address by querying multiple email-finding providers in sequence. If a match is found, the email is written to the lead's Work Email field. You can optionally add a verification step to confirm the address is valid before the automation continues.
The node runs instantly and follows a "waterfall" pattern: it tries each provider in the order you define, and stops as soon as one returns a result.
When to use it
Enrich leads before email outreach — add Find Email early in your automation so that by the time a lead reaches an email step, they already have a verified work address.
Maximize coverage with multiple providers — different providers have different databases. Chaining them in a waterfall means you'll find emails that any single provider would miss.
Ensure deliverability — add a verification provider to filter out invalid or risky addresses before sending.
How it works
Check skip conditions. Before searching, the node checks whether a search is necessary (see Skip conditions below). If not, it skips and the lead moves on without consuming any provider credits.
Run the waterfall. The node queries your configured providers one by one, in the order you set. As soon as a provider returns an email, the waterfall stops.
Verify (optional). If you've configured a verification provider, the found email is checked for deliverability before being saved.
Save the result. If an email was found, it's written to the lead's Work Email field. The lead's Email Status is set to Verified (if verification passed) or Unverified (if no verification provider was configured, or verification was inconclusive).
Branch. The lead exits through one of two branches depending on the outcome.
If a provider returns an error (e.g., rate limit, timeout), the node gracefully moves to the next provider in the sequence rather than failing the entire node. The node only fails if all providers error out.
Skip conditions
The node skips automatically (without querying any providers) in two cases:
No company domain. If the lead's company doesn't have a domain set, there's nothing to search against. The lead exits through the "not found" branch with the message "Email verification skipped, due to missing company domain."
Email already verified. If the lead already has a verified email address, the node doesn't search again. The lead exits through the "not found" branch with the message "Email verification already passed, skipping email search."
In both cases of skipping, no Email Finder credits are consumed.
Configuration
Search providers (waterfall sequence)
An ordered list of email-finding providers. The node tries them top to bottom and stops on the first hit. Drag to reorder.
Put your most reliable (or cheapest) provider first, and your broadest (or most expensive) provider last. This way, the fallback providers only fire when the primary one has no result — saving credits.
Verification provider (optional)
A single email-verification provider. When set, any email found by the waterfall is verified before being saved to the lead. If verification fails, the email is still saved but marked as Unverified.
If you don't set a verification provider, found emails are saved as Unverified immediately.
Branching
The node has two exit branches:
Branch | Condition |
Email found | The lead now has a work email (found by this node or already present). |
Not found | No provider returned a result, or the node was skipped (missing domain / already verified). |
Use the "Not found" branch to route leads to alternative flows — for example, try a LinkedIn message instead of email, or flag the lead for manual enrichment.
What gets written to the lead
Lead field | Value |
Work Email | The email address returned by the first successful provider. |
Email Status | Verified — if a verification provider was configured and the check passed. |
Tips
Always set the company domain. The node needs a company domain to search. If your leads are imported without company data, add an enrichment step (or a manual task) before the Find Email node.
Use verification if you plan to send email. Sending to unverified addresses hurts your sender reputation. Add a verification provider to avoid bounces.
Check Find Email credits. Each email enrichment query consumes at least 1 Find Email credit. If no credits are left, leads will fail.
Combine with a condition node. If you only want to search for emails on leads that meet certain criteria (e.g., job title, company size), put a condition node before Find Email to filter.
Limitations
Requires a company domain. If the lead's company has no domain, the node skips. It cannot search by name or LinkedIn URL alone.
No built-in delay or retry. The node runs instantly. If you need to throttle how fast emails are searched (e.g., to respect provider rate limits across many leads), add a Wait node before it.
Single email per lead. The node writes to the Work Email field. If the lead already has a work email that isn't verified, the node will overwrite it with the first result found.
Related articles
Automation Nodes — overview of all available node types.