n8n phone and email validation

Why validate inside n8n

The downloadable workflow turns up to 100 numbers into structured results. It removes exact duplicate inputs, calls LookupLab sequentially, and keeps the review decision beside each number. Nothing sends a text or updates your CRM automatically.

Use the same pattern on a lead trigger once you have tested a sample. Keep a stable record ID when connecting your CRM, and only recheck records when your freshness policy requires it.

Setup

1. Download the n8n JSON below. In n8n choose Import from File. The workflow is inactive and starts manually.
2. Create an HTTP Header Auth credential: name Authorization, value Bearer followed by your LookupLab API key. Select it in the LookupLab phone node.
3. Replace the sample list in Your phone list with your own E.164 numbers, such as +12025550123. Begin with two or three records.
4. Execute the workflow and inspect Review results. Outputs include number, valid, line_type, carrier, country, credits_charged and review.
5. HTTP failures stop the run. Check credentials for 401, balance for 402, or rate limits for 429. Inspect completed nodes before replaying to avoid paying again.

Walk through the complete workflow.
See the setup, sample output and review rules →

Phone validation is not consent, ownership verification or guaranteed delivery. Email syntax and MX checks establish domain-level signals, not proof that a particular mailbox exists.

What teams build with it

• Enrich a CRM import before uploading it.
• Review mobile, landline and VoIP contacts separately.
• Add carrier fields to a nightly data-quality workflow.

Related: ZapierMakeSlack