Lead Capture to Notion CRM with Alerts in Slack
Overview
This workflow instantly captures leads from any web form (Webflow, Tally, WordPress, custom HTML, etc.) and creates a new entry in your Notion CRM database while simultaneously sending a formatted alert to a Slack sales channel. It eliminates manual data entry and ensures your sales team can respond to leads within seconds of submission — no Zapier subscription required.
How It Works
The workflow is triggered by an incoming HTTP POST request (the webhook), then processes the lead data through two sequential actions: first creating a Notion database page, then posting a Slack message. The webhook responds immediately with a 200 status so the form never hangs or times out.
Node-by-Node Breakdown
-
Lead Webhook (No auth) — Listens for incoming POST requests at the path
/new-lead. Accepts both JSON and form-encoded payloads. When activated, n8n provides a unique production URL that you point your form's action attribute or integration to. The node responds automatically with HTTP 200 after all downstream nodes complete. -
Add to Notion CRM (OAuth2) — Creates a new database page in your specified Notion database. Configured parameters:
databaseId: The Notion database ID (must be replaced with your actual database ID)title: Set dynamically to{{ $json.body.name }}(the lead's name from the webhook payload)properties: Maps the lead's email to the "Email" property and sets a "Status" select property to "New"- Requires sharing your Notion database with the n8n integration
-
Alert Sales Channel (OAuth2) — Posts a formatted Slack message to a specified channel. Configured parameters:
channelId: The Slack channel ID (must be replaced with your actual channel)text: A dynamic message template using expressions::tada: New lead: *{{name}}* ({{email}})\n>{{message}}- Uses Slack's markdown formatting for bold text and blockquotes
Setup Instructions
Prerequisites
- An n8n instance (self-hosted or cloud)
- A Notion account with a Leads database (must contain at least Name, Email, and Status properties)
- A Slack workspace where you can create/choose a channel for lead alerts
- A web form or service that can send POST requests (Webflow, Tally, WordPress, Framer, custom HTML form, etc.)
Step-by-Step
- Activate the workflow in n8n and copy the production webhook URL from the Lead Webhook node (it will look like
https://your-n8n-instance.com/webhook/new-lead) - Configure your form to send a POST request to that URL with fields:
name,email, andmessage(JSON or form-encoded both work) - Connect Notion:
- Create an integration at https://www.notion.so/my-integrations
- Share your Leads database with that integration
- In n8n, create a Notion credential (OAuth2) and select your database
- Replace
REPLACE_WITH_DATABASEwith your actual database ID
- Connect Slack:
- Create a Slack app with
chat:writeandchannels:readscopes - Install the app to your workspace
- In n8n, create a Slack credential (OAuth2)
- Replace
REPLACE_WITH_CHANNELwith your actual channel ID (e.g.,C0123456789)
- Create a Slack app with
- Test: Submit a test lead through your form and verify it appears in Notion and Slack
Use Cases & Adaptations
Primary Use Cases
- Marketing teams: Capture leads from landing pages, webinar registrations, or content downloads
- Sales teams: Get instant notifications when high-value prospects submit inquiries
- Startups: Build a lightweight CRM without expensive tools
Variations to Try
- Add email automation: Insert a Gmail or SendGrid node after Notion to send an auto-reply to the lead
- Enrich lead data: Add an HTTP Request node to look up company info via Clearbit or Hunter.io
- Score leads: Use an n8n Code node to assign lead scores based on message content or source
- Multi-channel capture: Create additional webhook nodes for different forms, each routing to the same Notion database
- Error handling: Build a separate Error Trigger workflow that posts to Slack when any node fails
Required Replacements
Before running, you must replace these placeholder values:
REPLACE_WITH_DATABASE→ Your Notion database IDREPLACE_WITH_CHANNEL→ Your Slack channel ID
Workflow JSON
{
"name": "Lead Capture to Notion + Slack",
"nodes": [
{
"parameters": {
"content": "## Lead Capture Webhook to Notion CRM with Slack Alert\n\nEvery lead from any form lands in your Notion CRM and pings the team in Slack within seconds - no Zapier tax, no copy-paste.\n\n**Setup time:** 15 minutes · **Level:** Intermediate\n\n**You'll need accounts/credentials for:** Webhook, Notion, Slack\n\n**Replace these before running:**\n- `REPLACE_WITH_DATABASE`\n- `REPLACE_WITH_CHANNEL`\n\n**Setup steps:**\n1. Activate the workflow and copy the production webhook URL from the Webhook node.\n2. Point your form's action or integration at that URL (POST, JSON or form-encoded both work).\n3. Connect Notion, share your Leads database with the integration, and map the Name and Email properties.\n4. Connect Slack and choose the channel for alerts.\n5. Submit a test lead through your form and watch it appear in both places.\n\nFree templates and updates: navkhan103.github.io",
"height": 640,
"width": 400,
"color": 4
},
"id": "sticky-setup",
"name": "Setup — read me first",
"type": "n8n-nodes-base.stickyNote",
"typeVersion": 1,
"position": [
-440,
-40
]
},
{
"parameters": {
"content": "### How it runs\n\nStarts from **Lead Webhook**.\n\n1. A Webhook node gives you a URL you can point any form at (Webflow, Framer, Tally, WordPress, custom HTML).\n2. A Notion node creates a page in your Leads database with the name, email, and message.\n3. A Slack node posts a formatted alert to your sales channel so someone replies while the lead is hot.\n4. The webhook responds 200 immediately, so the form never hangs.",
"height": 348,
"width": 400,
"color": 7
},
"id": "sticky-how",
"name": "How it runs",
"type": "n8n-nodes-base.stickyNote",
"typeVersion": 1,
"position": [
-440,
640
]
},
{
"parameters": {
"content": "### If something breaks\n\nThe read and AI nodes here **retry 3× automatically** (5s apart), which absorbs rate limits and brief timeouts.\n\nNodes that **send or write deliberately do not retry** — a send that reached the far end but lost its response would otherwise fire twice, so you'd get duplicate messages or duplicate rows.\n\nTo be told when one of those fails, build a workflow starting with an **Error Trigger** node that posts to Slack or email, then set it under **three-dot menu > Settings > Error Workflow**. Do it once and point every workflow at it.",
"height": 400,
"width": 400,
"color": 3
},
"id": "sticky-fail",
"name": "If something breaks",
"type": "n8n-nodes-base.stickyNote",
"typeVersion": 1,
"position": [
-440,
1028
]
// ... truncated (copy to see full JSON)How to Import This Workflow
- 1Copy the workflow JSON above using the Copy Workflow JSON button.
- 2Open your n8n instance and go to Workflows.
- 3Click Import from JSON and paste the copied workflow.
Don't have an n8n instance? Start your free trial at n8nautomation.cloud
Related Templates
Extract Google Maps Business Leads via Dumpling AI to Google Sheets
Overview This workflow automates the extraction of business listings from Google Maps using Dumpling AI's search-maps API and logs the results into a structured Google Sheet. It's ideal for lead generation, market research, or competitive analysis — allowing you to quickly gather data like business names, ratings, addresses, phone numbers, websites, and booking links without manual browsing. Workflow Steps Trigger: Manual Test Run (Manual Trigger) — Starts the workflow on demand for testing. No authentication required. Search Google Maps via Dumpling AI (HTTP Request) — Sends a POST request to with a JSON body containing the search query (e.g., ) and language. Authentication uses Header Auth — you must provide a Dumpling AI API key as a header (configured in n8n credentials). The response returns an array of places with details like title, rating, address, phone, website, price level, and booking links. Split Places List for Processing (Split Out) — Splits the array from the HTTP response into individual items so each place can be processed separately. No authentication needed. Save Results to Google Sheet (Place Info) (Google Sheets) — Appends each place's data (name, address, rating, price level, type, website, phone, position, booking link) to a specified sheet in a Google Sheets document. Uses OAuth2 authentication (Google account). The sheet name is set to "Google Maps" and the document ID points to a spreadsheet named "Places". Setup Instructions Dumpling AI Account: Sign up at dumplingai.com and obtain an API key. In n8n, create a new Header Auth credential with the key name (e.g., ) and value . Google Sheets: Create a Google Sheet (or use the one referenced in the workflow). In n8n, create a Google Sheets OAuth2 credential by connecting your Google account. Ensure the sheet has a tab named "Google Maps" (or update the sheet name in the node). Customize Query: Edit the of the HTTP Request node to change the search query (e.g., ) or language. Run: Click "Execute Workflow" to test. The first run will prompt you to authorize Google Sheets access. Use Cases & Variations Lead Generation: Replace the query with industry-specific terms (e.g., "dentists in Los Angeles") to build a targeted prospect list. Competitor Analysis: Search for competitors in a niche and analyze their ratings, price levels, and online presence. Real Estate / Local Business Research: Extract data for multiple locations by chaining queries or using a loop. Automation: Replace the Manual Trigger with a Schedule Trigger to run daily/weekly, and add a Set node to dynamically pass queries from a spreadsheet or webhook. Enrichment: Add nodes to clean data, send notifications (Slack/Email), or integrate with a CRM like HubSpot.
Shopify New Order Slack Alert
High-Level Summary This workflow sends a real-time Slack notification whenever a new order is placed in your Shopify store. It listens for the webhook event, extracts key order details (customer name, line items, total), and posts a clean, formatted message to a Slack channel of your choice. No more refreshing the Shopify dashboard or digging through emails — every sale gets an instant cha-ching in Slack. Node-by-Node Walkthrough New Shopify Order (Shopify Trigger — OAuth2) — Subscribes to the webhook on your Shopify store. When a new order is created, this node fires and passes the full order object downstream. Authentication uses OAuth2 (or a Shopify Admin API access token) configured in the n8n credential store. Format Order (Code — No auth) — A JavaScript code node that extracts and transforms the raw order data. It builds a list of line items (), retrieves the customer's first and last name (falls back to "Guest"), and returns a clean JSON object containing , , , and (with currency). Post to Slack (Slack — OAuth2) — Sends a message to the specified Slack channel. The message uses n8n expressions to insert the formatted order data: a bold order number, total, customer name, and item list. The channel is set via a placeholder () that you must replace with your actual Slack channel ID or name. Authentication uses OAuth2 with scopes like and . Setup Instructions Shopify — You need a Shopify store with Admin API access. Create a custom app in your Shopify admin (Settings > Apps and sales channels > Develop apps). Grant it the scope, then generate an Admin API access token. In n8n, create a Shopify credential using OAuth2 or the access token. Slack — You need a Slack workspace where you have permission to create apps. Create a Slack app, enable OAuth2, and add the and scopes. Install the app to your workspace and copy the OAuth token. In n8n, create a Slack credential with that token. Replace the placeholder — In the Post to Slack node, change to the actual channel ID (e.g., ) or channel name (e.g., ). Activate the workflow — Once everything is connected, activate the workflow. Place a test order in your Shopify store (or use Shopify's webhook tester) to verify the alert appears in Slack. Use Cases & Variations Real-time sales tracking — Perfect for small teams or solo entrepreneurs who want to celebrate every order as it happens. Multi-channel notifications — Add an email node (e.g., Gmail or SendGrid) to also send a receipt or summary to the store owner. Order analytics — Insert a Google Sheets node after the trigger to log every order for later analysis. Other Shopify events — Change the trigger topic to , , or to monitor different stages of the order lifecycle. Custom formatting — Modify the Code node to include shipping address, discount codes, or payment status.