Manage Webflow Form Submissions in Discord

Imagine this for a second: you launch a new Webflow form, people start filling it out, and suddenly your inbox looks like it went through a glitter explosion. You are copying form data into Discord, creating channels manually, tagging teammates, pasting messages, and doing the same routine over and over.

At some point you probably think, “Surely I do not have to be the copy-paste person forever, right?”

Good news, you really do not. With a ready-made n8n workflow template, you can hook Webflow to Discord so that:

• Discord channels are created automatically from your Webflow form names
• Every new submission lands in the right channel
• Your team can see and discuss everything in one place

Let us walk through what this template actually does, when you would want to use it, and how to get it running without turning setup into a whole side project.

What This n8n Workflow Template Does For You

At its core, this workflow connects Webflow forms with your Discord server so each form has its own dedicated space for conversations. Instead of emails and scattered screenshots, everything flows into Discord automatically.

Here is the big-picture flow of the automation:

• Listens for Webflow form submissions with a Webflow trigger node
• Checks your Discord server for a channel that matches the form name
• Creates a new Discord channel if one does not exist yet
• Notifies your #general channel whenever a new form channel is created
• Formats the submission as markdown so the message is clean and readable
• Sends the formatted submission into the correct Discord channel

The end result is simple and really useful: every Webflow form gets its own “home” in Discord, and every submission is posted where your team can actually see it, talk about it, and follow up.

Why Connect Webflow Forms To Discord With n8n?

If Webflow is where you collect information and Discord is where your team hangs out, connecting them is kind of a no-brainer. This workflow helps you go from “we will organize this later” to “wow, this actually runs itself.”

Here is what you gain by automating the connection:

• Centralized information
  No more hunting through inboxes, random DMs, or half-forgotten spreadsheets. Everything is in Discord, in clearly named channels.
• Faster responses
  Submissions show up in real time in channels your team already watches, so it is easier to reply quickly.
• Better organization
  Each Webflow form gets its own Discord channel, which makes it simple to track conversations and decisions related to that specific form.
• Clear records
  Instead of submissions getting buried in email archives, they are logged in a dedicated channel that anyone on the team can revisit.

In short, you get a lightweight system that keeps things tidy without you needing to babysit every form submission.

How The Workflow Actually Works (Step By Step)

Let us peek under the hood and follow what happens from the moment someone hits “Submit” on your Webflow form to the moment your team sees the message in Discord.

1. Webflow Trigger Listens For New Form Submissions

The workflow starts with a Webflow trigger node. This node listens for new submissions on your Webflow site and grabs two key pieces of information:

• The form name, which is later used to decide which Discord channel to use or create
• The form data, which includes all the field values you want to send to Discord

As soon as someone submits a form, the workflow kicks into motion automatically.

2. n8n Pulls a List of All Discord Channels

Next, the workflow talks to the Discord API to list all channels in your chosen guild (server). This gives n8n a full list of existing channels so it can check if there is already one that matches the form.

Think of it like asking Discord, “What channels do we already have to work with?”

3. JavaScript Code Cleans Up The Form Name

Now a JavaScript code node steps in to transform the Webflow form name into a Discord-friendly channel name. It:

• Converts the form name to lowercase
• Replaces spaces with hyphens
• Compares this cleaned-up name to the list of channels from your server

For example, a form called “Contact Us” becomes contact-us. If a channel with that name already exists, great. If not, the workflow gets ready to create one.

4. IF Node Checks If The Channel Already Exists

An IF node then decides which path the workflow should follow based on the previous step:

• If the channel exists: The workflow skips channel creation and jumps straight to formatting and posting the submission.
• If the channel does not exist: It creates a new channel, sends a notification to #general, and then posts the submission in that new channel.

This check is what keeps your server from ending up with duplicate channels that differ only by a space or underscore.

5. Creating a New Discord Channel From the Form Name

When there is no matching channel, the workflow uses the Discord API to create a new text channel with a clean, consistent naming style:

• All lowercase
• Spaces replaced with hyphens

So you do not end up with a mix like “Contact Us”, “contact-us”, and “contact_us_but_different”. Everything follows the same pattern, which makes your channel list much easier to scan.

6. Notifying The #general Channel About New Channels

Whenever a new channel is created, the workflow posts a notification message in #general. That message includes a direct link to the new channel so your team can jump in quickly.

This is especially useful when you roll out a brand new form and want everyone to know where those submissions will be discussed.

7. Formatting Submission Data as Markdown

Before sending anything to Discord, another JavaScript code node takes the raw form data and turns it into a nicely formatted markdown message. That way, what shows up in Discord is easy to read at a glance.

For example, instead of raw JSON, you get something like:

**New Webflow Form Submission**
- Name: Jane Doe
- Email: jane@example.com
- Message: I would love to learn more!

Much nicer than a messy blob of data, right?

8. Posting The Submission To The Correct Discord Channel

Finally, the workflow sends that markdown message to the right place. Depending on the earlier IF check, the message will be posted to:

• An existing channel that already matches the form name, or
• The newly created channel that was just set up for this form

Either way, every submission ends up in a consistent, predictable location that your team can rely on.

Benefits of Automating Webflow To Discord With n8n

Once this workflow is live, you get a bunch of quality-of-life upgrades without really thinking about it.

• Automation: No more manual channel creation or copy-paste routines for every single submission.
• Organization: Each Webflow form has its own dedicated Discord channel, so discussions stay focused and easy to follow.
• Real-time notifications: Submissions appear in Discord as they happen, not whenever someone remembers to check email.
• Flexibility: Because this runs in n8n, you can extend it later to ping other tools, trigger additional bots, or add more logic.

In other words, you trade repetitive admin work for an automation that quietly does its job in the background.

What You Need Before You Start

Before this template can do its magic, you will need a couple of credentials ready to plug into n8n. Here is a quick checklist.

1. Create Webflow API credentials (V1 Token)
   Open your Webflow project settings and generate a V1 API token. You will use this token to authenticate the Webflow nodes in n8n so they can listen for form submissions.
2. Set up Discord Bot API credentials
   Go to the Discord Developer Portal, create or select an application, and configure a bot. This gives you the bot token and related credentials that n8n uses to:
   • List channels in your server
   • Create new channels
   • Send messages into those channels
3. Connect your credentials inside n8n
   In your n8n instance, open the workflow template and link:
   • Your Webflow API token to the Webflow trigger node
   • Your Discord bot credentials to the Discord nodes that:
     • List channels
     • Create channels
     • Send messages
4. Activate and test the workflow
   Turn the workflow on, then submit a test form on your Webflow site. You should see:
   • A new Discord channel created if one did not already exist for that form
   • A notification in #general when the new channel is created
   • The nicely formatted submission message in the channel that matches the form

Tips To Get The Most Out Of This Template

A tiny bit of planning makes this setup even smoother and more useful long term. Here are a few practical tweaks you can make.

• Use meaningful Webflow form names
  Since channel names are generated from form names, choose names that are clear and unique. For example, job-application is much more helpful than form-1.
• Keep channel names descriptive
  As your server grows, descriptive names make it easier for your team to quickly understand what each channel is for.
• Customize the #general notification message
  Adjust the text that gets posted in #general so it matches your team’s style, whether you prefer playful, formal, or something in between.
• Test with different forms and edge cases
  Try multiple forms, unusual field values, and different naming patterns. Make sure the channel naming and markdown formatting behave the way you expect before rolling it out widely.

Next Steps: Let The Automation Handle The Boring Stuff

If you are tired of babysitting form submissions and juggling copy-paste tasks, this n8n workflow template is a simple way to reclaim some time and keep your team in sync.

Set it up once, connect your Webflow and Discord credentials, and from then on your forms and channels stay aligned with almost no effort on your part.

Want a deeper walkthrough with more detail and a video demo? Check out the full guide with video.

When you are ready to plug this into your own n8n instance, grab the template below and start automating your way out of repetitive work.