Lead Intake Webhook to Airtable + Slack Routing (n8n Workflow)

Turn every lead submission into an Airtable record and the right Slack alert—automatically

This n8n workflow receives leads via a secured webhook, validates and de-duplicates them against Airtable, saves new leads, and then posts to the correct Slack channel based on programme—returning clear HTTP responses for each outcome.

What this workflow does

• Receives lead data via a POST request to the /lead-intake webhook using header-based authentication.
• Normalizes and validates fields (from body or root). If required details are missing or invalid, it responds with HTTP 400 and error details.
• De-duplicates leads by searching Airtable for an existing record where the Email field matches the submitted email.
• If a match is found, it returns HTTP 200 with a duplicate response and stops.
• Creates new leads in Airtable with the submitted details plus routing metadata.
• Routes Slack notifications: enquiries with “Computer Science” go to a priority Slack channel; all others go to a general Slack channel, then returns HTTP 200 for created.
• If the Airtable lookup or create fails, it posts an alert to a Slack failure/monitoring channel and returns HTTP 500.

Use cases

• Capture form/app lead submissions and instantly register them in your Airtable Leads table.
• Prevent duplicate lead spam by matching on Email before creating records.
• Route urgent “Computer Science” enquiries to a priority Slack channel for faster follow-up.

Technical details

• Nodes/logic used: webhook, if, set, switch, airtable, slack.
• Integrations: Airtable via Personal Access Token; Slack channel notifications.
• Setup requirements: configure header-auth token, update Airtable base/table IDs, and ensure Airtable fields include Name, Email, Phone, Country.