How to find email addresses in an n8n workflow

The gap between "I know who" and "I can reach them"

Plenty of workflows get you to a name and a company and then stall. A lead fills in a form with their name and employer. A mention surfaces an interesting person at a known company. A list import has everything except the one field that matters for outreach: the email. Without an address, the record is a dead end, and chasing each one by hand — guessing patterns, checking, hoping — is slow and unreliable.

Automating email discovery in n8n closes that gap, and the MentionFox Find Email node is the step that does it. The instant you have a person and a domain, a find-email step can resolve a reachable address and write it back, so the record arrives ready to act on. But there is a right way and a wrong way to do this, and the wrong way is expensive in a way that does not show up until later.

Why verification is the whole game

The naive approach to "find an email" is to guess. Take a name, take a domain, assemble the usual patterns — first.last, first, finitial-last — and send. This feels free, and it quietly destroys your deliverability. Every guess that is wrong bounces. A high bounce rate tells mailbox providers you are not a careful sender, and they respond by routing all your mail — including the messages to people who genuinely want to hear from you — into spam. One careless campaign of guessed addresses can degrade sending reputation for weeks.

Verified discovery is the opposite. A good find-email step does not just assemble a plausible address; it checks that the mailbox actually exists before handing it to you, and tells you whether it is verified. You only ever send to addresses that have been confirmed, which keeps your bounce rate low and your reputation intact. In automation especially, this matters more, because you are sending at volume and a fabricated address scales into a fabricated-address problem fast.

The find-email workflow in n8n

The shape is small and reusable:

1. A source of person + domain. This can be a form submission, a new sheet row, a webhook from your CRM, or the output of an earlier step in a larger workflow. The only required input is the company domain; a name sharpens the result considerably.
2. A find-email node. Give it the domain and, ideally, the person's name. It returns the best verified work email, a verified flag, and — usefully — charges nothing when no email can be found.
3. A branch on the result. If an email came back, write it to your CRM or sheet and continue to whatever is next. If not, route the record to a "no email" lane so a human can decide whether to find another path or drop it.

For records that start as just a name and company, pair find-email with enrichment: find the address first, then enrich the person around it to fill in title, links, and confidence. That combination produces the most complete, immediately-usable contact.

Running it over a list

The same node works one-at-a-time from a trigger or in bulk over a list. Point it at a sheet of names and domains, let n8n iterate, and collect verified emails into a new column — with the misses clearly marked rather than filled with guesses. Because the node charges only on a match, running it across a list of mixed quality does not punish you for the domains that have nothing discoverable; you pay for the addresses you actually get.

Cost, and the pay-on-success model

Email discovery is a paid operation because verification does real work. The important detail is the billing shape: a real match costs credits, and a miss costs nothing. That pay-on-success model changes how you can use it — you can run it speculatively over a list, or on every inbound lead, without worrying that the dead ends will run up the bill. Combined with verification protecting your sending reputation, it makes automated email finding both safe and economical. Credit packs are on the pricing page.

Good-sender hygiene, automated

Finding the address is only half of being a good sender; the other half is how you use it. Automation makes it easy to do the right things consistently, if you wire them in. Warm a new sending domain gradually rather than blasting from cold. Keep your list clean by routing the misses out instead of retrying them forever. Respect unsubscribes and regional consent rules — an n8n branch can check a suppression list before any send path. And never let discovery feed an auto-send: the point of finding a verified email is to enable a thoughtful message a human reviews, not to fire a templated blast the moment an address resolves. These habits are not extra work when they live in the workflow; they are nodes you set up once and forget. The result is a system that finds reachable people and reaches them in a way that keeps your domain trusted, which is the only way outreach stays viable past the first month.

It also pays to keep a record of where each address came from and when it was verified, so a stale contact can be re-checked rather than blindly reused. A verified email is a point-in-time fact; people change jobs. Logging the verification timestamp alongside the address lets a later workflow flag contacts that are old enough to re-confirm before the next campaign.

Where this lands: the MentionFox n8n template Inbound Lead Webhook → Find Email + Enrich → Airtable wires verified email discovery end to end, and you can swap its webhook for a sheet read to run it over a whole list. The MentionFox Find Email node charges only on a match and runs on your FoxAPIs credits — key at foxapis.com.

On credits: the MentionFox n8n node runs on FoxAPIs credits — priced at foxapis.com/pricing and separate from MentionFox subscription plans. Get your free API key at foxapis.com/trial.

Questions, answered