Webflow to Slack, every form lead in the right channel
Your Webflow forms are working, but your lead routing is a mess. One inbox gets everything, notifications get buried, and someone ends up copying details into Slack by hand (or worse, forgetting).
This Webflow Slack automation hits marketing managers first, but sales leads and client ops feel it too. You get every form submission posted to the right Slack channel automatically, so the right people see it fast and you can actually follow up.
Below, you’ll see how the workflow creates channels per form, formats each submission cleanly, and alerts #general when a brand-new form appears.
How This Automation Works
See how this solves the problem:
n8n Workflow Template: Webflow to Slack, every form lead in the right channel
flowchart LR
subgraph sg0["Webflow Form Submission Flow"]
direction LR
n0@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Does the channel exist?", pos: "b", h: 48 }
n1["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/slack.svg' width='40' height='40' /></div><br/>Send slack message to channel"]
n2["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/slack.svg' width='40' height='40' /></div><br/>Create Slack channel with fo.."]
n3@{ icon: "mdi:swap-vertical", form: "rounded", label: "Transform data to send message", pos: "b", h: 48 }
n4["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/slack.svg' width='40' height='40' /></div><br/>Notify #general channel of n.."]
n5["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/webflow.svg' width='40' height='40' /></div><br/>Webflow Form Submission Trig.."]
n6["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Compose Slack message"]
n7["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/slack.svg' width='40' height='40' /></div><br/>List Slack Channels"]
n8["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Check if Webflow form has an.."]
n7 --> n8
n6 --> n1
n0 --> n6
n0 --> n2
n3 --> n6
n5 --> n7
n2 --> n3
n2 --> n4
n8 --> n0
end
%% Styling
classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef disabled stroke-dasharray: 5 5,opacity: 0.5
class n5 trigger
class n0 decision
class n6,n8 code
classDef customIcon fill:none,stroke:none
class n1,n2,n4,n5,n6,n7,n8 customIcon
The Challenge: Form leads land in the wrong place
Webflow’s default form notifications are fine when you’re a one-person show. Then the site grows. Now you have a “Contact” form, a “Get a quote” form, a “Book a demo” form, and maybe a couple hidden forms inside templates. Everything still emails one person, which means leads get triaged manually, forwarded to teammates, and re-explained in Slack. The cost isn’t just time. It’s missed speed-to-lead, messy handoffs, and zero consistent record of what came in and where it went.
It adds up fast. Here’s where it breaks down in real teams.
- Someone has to read the email, decide who should see it, and then forward or paste it into the right Slack channel.
- Different forms need different owners, but everything arrives in the same place so routing becomes guesswork.
- Important context gets lost because the same lead is retyped, shortened, or “summarized” during handoff.
- New forms quietly go live and nobody updates the process, so submissions disappear until a customer complains.
The Fix: Webflow forms routed into dedicated Slack channels
This workflow listens for new Webflow form submissions, figures out which form the submission came from, and makes sure there’s a matching Slack channel for it. If the channel already exists, it posts a formatted message right there so the right team sees it in context. If the form is brand new, it creates the Slack channel automatically, then posts the submission. It also sends a message to your #general channel with a hyperlink to the newly created channel, so everyone knows a new intake path now exists. No more inbox triage, no more copy-paste, and way less “did anyone see this lead?” chasing.
The workflow starts with a Webflow intake trigger whenever a form is submitted. It pulls your existing Slack channels, checks if there’s already a channel mapped for that form, and then either posts immediately or creates the new channel first. Finally, it posts the lead details in a clean Slack Block format and pings #general when a new form channel is introduced.
What Changes: Before vs. After
| What This Eliminates | Impact You’ll See |
|---|---|
|
|
Real-World Impact
Say you run 5 active Webflow forms and you average 12 submissions a day. Manually, it’s maybe 5 minutes to read the email, figure out who needs it, paste the details into Slack, and answer the inevitable “which form was this?” question. That’s about an hour a day of pure routing. With this workflow, the “work” is basically zero: Webflow triggers it instantly, Slack messages land in the right channel, and new forms create their own channels automatically.
Requirements
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Webflow to trigger on new form submissions.
- Slack to create channels and post messages.
- Webflow API access (get it from your Webflow account settings).
Skill level: Beginner. You’ll connect Webflow and Slack, then adjust a couple naming and routing conventions.
Need help implementing this? Talk to an automation expert (free 15-minute consultation).
The Workflow Flow
A Webflow form submission triggers everything. The moment someone fills out a form on your site, n8n receives the payload (name, email, message, and whatever custom fields you’ve added).
Slack channels get checked against the form name. The workflow retrieves your current Slack channel list, then evaluates whether a channel already exists for that specific Webflow form (using a small logic step to match names consistently).
If the channel is missing, it’s created. When a new form is detected, n8n generates the Slack channel first, maps the message payload, and also posts a heads-up in #general with a link to the new channel so your team notices the change.
The submission is posted as a formatted Slack message. Instead of a messy paragraph, the workflow builds Slack Blocks and posts a readable lead card into the right channel, which means less back-and-forth and fewer follow-up questions.
You can easily modify the channel naming convention to match your Slack standards (for example, “leads-webflow-contact” instead of “contact-form”). See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Webflow Trigger
Set up the workflow to listen for new Webflow form submissions.
- Add the Webflow Intake Trigger node as the trigger.
- Set the Site field to
60e6f0f07c46af62aa2b1c98. - Credential Required: Connect your webflowApi credentials in Webflow Intake Trigger.
Step 2: Connect Slack and Retrieve Channels
Fetch all Slack channels so the workflow can determine whether a form-specific channel already exists.
- Add the Retrieve Slack Channels node and connect it after Webflow Intake Trigger.
- Set Resource to
channeland Operation togetAll. - Enable Return All with
trueand ensure archived channels are excluded. - Credential Required: Connect your slackApi credentials in Retrieve Slack Channels.
Step 3: Evaluate and Route by Channel Presence
Transform the form name, check if a matching Slack channel exists, and branch accordingly.
- Add Evaluate Form Channel after Retrieve Slack Channels and keep the provided JavaScript to transform the form name and map channels.
- Add Validate Channel Presence after Evaluate Form Channel and set the condition to
{{ $json.channel }}with the notEmpty operator. - Connect the true output of Validate Channel Presence to Build Slack Blocks, and the false output to Generate Slack Channel.
Step 4: Build and Deliver Slack Messages
Construct the Slack message blocks, create channels when needed, and post notifications.
- In Build Slack Blocks, keep the JavaScript that formats formData into Markdown and creates
slackMessageBlock. - Configure Post to Slack Channel with Message Type set to
block, Blocks set to{{ JSON.stringify($json.slackMessageBlock) }}, and Channel ID set to{{ $json.channel.id }}. - Credential Required: Connect your slackApi credentials in Post to Slack Channel.
- Configure Generate Slack Channel with Resource set to
channeland Channel ID set to{{ $json.formName }}. - Credential Required: Connect your slackApi credentials in Generate Slack Channel.
- Generate Slack Channel outputs to both Map Message Payload and Alert General Channel in parallel.
- In Map Message Payload, keep Include set to
noneand map fields using expressions like{{ $('Evaluate Form Channel').item.json.formData }}and{{ $('Evaluate Form Channel').item.json.formName }}. - Configure Alert General Channel with Message Type set to
blockand keep the provided Blocks template. - Credential Required: Connect your slackApi credentials in Alert General Channel, and replace Channel ID with your Slack general channel ID.
[YOUR_ID], the message will fail. Replace it with your actual Slack channel ID.Step 5: Test and Activate Your Workflow
Verify the workflow end-to-end before activating it in production.
- Click Execute Workflow and submit a test form in Webflow to trigger Webflow Intake Trigger.
- Confirm that Retrieve Slack Channels returns channels and Evaluate Form Channel produces
formNameandformData. - Verify that messages appear in the correct Slack channel via Post to Slack Channel, and that Alert General Channel posts when a new channel is created.
- When successful, switch the workflow to Active to run it automatically for live submissions.
Watch Out For
- Slack credentials can expire or need specific permissions. If things break, check the n8n Credentials panel and your Slack app scopes first.
- Channel creation can fail if the name already exists in a slightly different format (pluralization, underscores, or a legacy channel). Standardize your naming logic in the “Evaluate Form Channel” step.
- Formatted Slack Blocks look great, but they’re picky. If fields are missing from some submissions, make your “Build Slack Blocks” logic resilient so the post doesn’t fail on empty values.
Common Questions
Usually about 30 minutes if your Webflow and Slack access is ready.
Yes. You won’t write code, but you will connect accounts and decide a channel naming convention.
Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in Slack/Webflow costs (typically none beyond your existing plans).
Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.
You can. Most customizations happen in “Evaluate Form Channel” (how you match forms to channels) and “Build Slack Blocks” (how the message looks). Common tweaks include routing certain forms to an existing channel instead of creating a new one, adding an “owner” mention for your responder, and renaming channels to match your internal taxonomy.
Usually it’s expired credentials or missing scopes for channel listing/creation. Reconnect Slack in n8n and confirm the app is allowed to read channels and post messages. If it fails only when creating channels, your workspace may restrict who can create new channels, which means you’ll need an admin-approved app or a different routing approach.
Plenty for most small teams.
Often, yes, especially if you want the “create a channel if it doesn’t exist” logic and clean message formatting in the same flow. n8n makes it easier to retrieve channels, evaluate naming rules, and branch without paying extra for every path. It also gives you self-hosting, which is handy if you’re processing lots of submissions. Zapier or Make can be quicker for a basic “Webflow to Slack message” setup, but they tend to get awkward when you add dynamic channel management. Talk to an automation expert if you want help choosing.
Once this is live, leads stop drifting into the wrong inbox and start landing where work actually happens. Set it up once, then let Slack do what it’s good at.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
