Send lead notifications and acknowledgements via webhook, Gmail and Data Tables
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 15 nodes and runs when an HTTP POST request hits its webhook URL. Along the way it connects Gmail.
How it runs
Trigger: When an HTTP POST request hits its webhook URL.
- Normalize Lead Data (Edit Fields (Set)): sets 8 fields: leadId, leadName, leadEmail…
- Validate Lead Input (If): checks a condition and branches into true / false
- Check Duplicate Notification (Data table): get (row)
- Respond - Invalid Payload (Respond to Webhook): sends the response back to the webhook caller
- Is Duplicate Notification? (If): checks a condition and branches into true / false
- Respond - Already Notified (Respond to Webhook): sends the response back to the webhook caller
- Prepare Notification Payload (Edit Fields (Set)): sets 7 fields: leadId, leadName, leadEmail…
- Notify Admin (Gmail): send (message)
- Send Acknowledgement to Lead (Gmail): send (message)
- Record Admin Email Result (Edit Fields (Set)): sets 4 fields: leadId, executionId, adminEmailStatus…
…plus 4 more steps. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (7)
- Webhook
n8n-nodes-base.webhook - Edit Fields (Set)
n8n-nodes-base.set - If
n8n-nodes-base.if - Data table
n8n-nodes-base.dataTable - Respond to Webhook
n8n-nodes-base.respondToWebhook - Gmail
n8n-nodes-base.gmail - Merge
n8n-nodes-base.merge
From the author
Quick overview This workflow receives new lead submissions via a header-authenticated webhook, validates and normalizes the payload, prevents duplicate notifications using an n8n Data Table, then sends two Gmail emails (admin alert and lead acknowledgement)…