Intake and route web form leads with Airtable and Slack
Ready for 3.0What this workflow does
This workflow has 17 nodes and runs when an HTTP POST request hits its webhook URL (plus 1 other trigger). Along the way it connects Airtable and Slack.
How it runs
Trigger: When an HTTP POST request hits its webhook URL (plus 1 other trigger).
- Validate Submission (Edit Fields (Set)): sets 8 fields: name, email, phone…
- Alert Error Channel (Slack): uses Slack
- Is Valid? (If): checks a condition and branches into true / false
- Find Existing by Email (Airtable): search
- Respond 400 Invalid (Respond to Webhook): sends the response back to the webhook caller
- Errored? (If): checks a condition and branches into true / false
- Notify Failure Channel (Slack): uses Slack
- Is Duplicate? (If): checks a condition and branches into true / false
- Respond 500 Failure (Respond to Webhook): sends the response back to the webhook caller
- Respond 200 Duplicate (Respond to Webhook): sends the response back to the webhook caller
…plus 5 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 (8)
- Webhook
n8n-nodes-base.webhook - Edit Fields (Set)
n8n-nodes-base.set - If
n8n-nodes-base.if - Airtable
n8n-nodes-base.airtable - Respond to Webhook
n8n-nodes-base.respondToWebhook - Switch
n8n-nodes-base.switch - Slack
n8n-nodes-base.slack - Error Trigger
n8n-nodes-base.errorTrigger
From the author
Quick overview This workflow receives lead submissions via a secured webhook, validates and de-duplicates them against Airtable, stores new leads in an Airtable base, and notifies the appropriate Slack channel based on programme, returning clear HTTP…