Validate email deliverability via webhook using Google and Cloudflare DNS

by Fred Carbonare · 17 views · created 2026-08-28 · Document Extraction

What this workflow does

This workflow has 12 nodes and runs when an HTTP GET request hits its webhook URL. It uses only n8n's built-in nodes. It also calls dns.google and cloudflare-dns.com over HTTP.

How it runs

Trigger: When an HTTP GET request hits its webhook URL.

1. Extract email and domain (Edit Fields (Set)): sets 2 fields: email, domain
2. Check email syntax (If): checks a condition and branches into true / false
3. Google DoH — MX lookup (HTTP Request): calls dns.google
4. Respond 400 — invalid syntax (Respond to Webhook): sends the response back to the webhook caller
5. Has MX records? (Google) (If): checks a condition and branches into true / false
6. Cloudflare DoH — MX lookup (fallback) (HTTP Request): calls cloudflare-dns.com
7. Respond 200 — deliverable (Google) (Respond to Webhook): sends the response back to the webhook caller
8. Respond 200 — no MX (Google) (Respond to Webhook): sends the response back to the webhook caller
9. Has MX records? (Cloudflare) (If): checks a condition and branches into true / false
10. Respond 200 — deliverable (Cloudflare) (Respond to Webhook): sends the response back to the webhook caller

…plus 1 more step. See the full node list below.

HTTP calls to: dns.google, cloudflare-dns.com

Before you upgrade to n8n 3.0

Nodes used (5)

• Webhookn8n-nodes-base.webhook
• Edit Fields (Set)n8n-nodes-base.set
• Ifn8n-nodes-base.if
• HTTP Requestn8n-nodes-base.httpRequest
• Respond to Webhookn8n-nodes-base.respondToWebhook

From the author

Quick Overview This workflow exposes a webhook that validates an email’s deliverability by checking whether its domain has DNS MX records, using Google DNS-over-HTTPS with an automatic fallback to Cloudflare, and returns a JSON verdict with the reason and…

View the original on n8n.io → Check your own copy