Open-source n8n templates for bulk email verification

Description and use

n8n templates for bulk email verification separate leads into safe, review, and drop lists, handling provider quirks and domain reordering, and expose a webhook for real‑time signup validation.

Problem

Email lists often contain invalid or risky addresses that waste resources when used in sequences, CRMs, or agent workflows.

Outcome

The templates enable batch verification of email addresses, producing consistent verdicts and scores, and separating safe, review, and drop lists. They handle domain reordering, greylisting, and provider-specific quirks, and expose a webhook for real‑time signup validation.

Workflow

• Read input data (Google Sheets rows or CSV upload).
• Send addresses in batches to an email‑verification API via HTTP Request node.
• Match results back to original records by address, not row order.
• Write status, score, and check keys back to the source (Sheets or CSV).
• Generate separate lists (send_safe, review, drop) for CSV workflow.
• Return allow/review/block verdict for signup webhook.
• Use AI agent tool to interpret results and decide actions.

Evidence

I built a set of four n8n templates around one job: checking whether email addresses are worth sending to, before they go into a sequence, a CRM, or an agent's hands.

Source

Results are matched back by address, not row order. The verifier groups addresses by domain, so they come back reordered; matching by position silently writes the wrong verdict on the wrong row.

Source

Everything uses the core HTTP Request node (no community node) and a Header Auth credential, so nothing secret lives in the JSON.

Source

The templates are MIT, but they call an email-verification Actor I built and run on Apify, which is pay-per-verified-address (there's a free tier).

Source