Discord

Connecting Discord to your Webflow site pushes form signups, orders, and CMS updates straight into your channels the moment they happen. No dashboard checks, no email digest lag. You can also embed a Discord server widget on any page so visitors see live community activity and join without a separate invite step.

Most flows run through incoming webhooks with no bot required, making this a fit for community managers, content creators, course operators, agencies, and SaaS founders routing form submissions into a dedicated ticket or moderation channel.

How to integrate Discord with Webflow

What is Discord? Discord a communications platform built around servers and channels. Originally made for gaming communities, it is now used for community building across many verticals. The Discord Developer Platform supports bots, apps, and activities, and it exposes incoming webhooks that let external services POST a JSON payload to a channel without a bot or persistent connection.

Connect Discord and your site when you want site activity to show up where your community already talks. Form submissions and other site events land in a channel within seconds. On the front end, a Discord widget lets visitors see who is online before they join.

There's no official Discord app in the Marketplace. You have three approaches for pairing Discord with your site:

• The Discord server widget with Code Embed adds live community activity to a page without writing backend code.
• Automation platforms like Zapier, Make, n8n, and IFTTT connect site triggers to Discord actions with no code.
• The Webflow Data API and Discord APIs give you full control over webhook delivery and CMS sync, but require server-side middleware.

Most setups combine two or more of these methods depending on complexity.

Add a Discord server widget with Code Embed

This method requires no code and displays your Discord server directly on a page of your site. Discord generates an HTML or JSON widget from your server settings. Paste that markup into a Code Embed element. Visitors then see online members and can join a recruitment or community channel without needing a manual invite. You only need Discord's widget code and a Code Embed element.

To set up the widget:

1. In Discord, open Server Settings > Widget and enable the widget, then adjust invite settings and copy the HTML or JSON code.
2. Drag a Code Embed element onto the page where you want the widget.
3. Paste the copied markup and publish the site to render it.

This method supports a few practical outcomes:

• Show live server activity so recruits see how active your community is before joining.
• Provide a direct join path through an embedded invite link.
• Surface the widget on a landing or about page so prospective members see real-time activity in context with your other content.

The Code Embed element renders only on the published site or in Preview mode, and it caps at 50,000 characters. You need a paid site plan to use Code Embed and custom code in head and body tags. The free Starter plan doesn't support them.

For static join links, skip the widget entirely. Drag any button or text link onto the page and point it at a Discord invite URL. Invite links need no paid plan and follow the rules in Discord's Invites 101 guide, including 7-day, 30-minute temporary, and non-expiring options.

Connect with Zapier, Make, n8n, or IFTTT

Automation platforms connect site triggers to Discord actions without code, and they handle the middleware for you. This is the most common path for posting form submissions and other site activity to a channel. Zapier has the most pre-built templates for this pairing, while n8n suits complex routing like creating channels based on form type.

Zapier supports a direct Webflow ↔ Discord connection with ready-made Zap templates. Available connections include:

• New Webflow form submission → send a Discord channel message
• New Webflow form submission → add a Discord role
• New Webflow order → create a Discord channel message
• New Discord channel message → create a new Webflow item
• New Discord reaction → update a Webflow live item

Zapier also supports Webflow-triggered Discord workflows for form submissions, orders, comments, and resolved comment threads, along with Discord-triggered Webflow item updates.

Make supports the same pairing with custom scenarios. Use Make for Webflow Watch Comment Threads → Discord message or thread workflows, Webflow Watch Events → Discord channel message workflows, and Webflow event → Discord role, channel, event, or reaction workflows.

n8n connects the two through built-in nodes for Webflow CMS item operations and Discord messaging. Use n8n for Discord message → Webflow CMS item workflows, Webflow CMS item → Discord message workflows, or multi-step routing that combines both. A published template syncs Webflow form leads to Pipedrive with Discord and Gmail notifications.

IFTTT also has a dedicated Webflow ↔ Discord connection, including an applet to create a new Webflow collection item from a Discord message.

Pick the platform that matches your routing needs and existing tooling, and move to the API path when you need full control over payload formatting.

Build with the Webflow Data API and Discord APIs

The API path gives you full control over message formatting and trigger logic. You need server-side development because neither platform POSTs directly to the other. Site webhooks deliver payloads to a middleware or serverless function, and that middleware calls Discord's Execute Webhook endpoint. Take this path when you need custom embed formatting or workflows like conditional routing and Discord-initiated CMS updates.

The integration uses these APIs:

• The Discord webhook API handles posting messages to a channel through the Execute Webhook endpoint, POST /api/v10/webhooks/{webhook.id}/{webhook.token}
• The Webflow Data API handles CMS collections and form submissions, while webhook registration covers setup details
• Webflow webhooks trigger real-time events like form_submission and site_publish

You need a Bearer token for all Data API requests, while Discord webhook execution needs no bot token because the token is embedded in the URL.

Post Webflow form submissions to a Discord channel

This is the most common API-based flow. A form submission fires a site webhook to your middleware, which formats the data and posts it to Discord. You get a real-time alert in a channel such as #support-tickets or a private moderation channel.

To implement this:

1. In Discord, open Server Settings > Integrations > Webhooks > New Webhook and copy the webhook URL, which looks like https://discord.com/api/webhooks/{webhook.id}/{webhook.token}.
2. Register a site webhook with POST /v2/sites/{site_id}/webhooks using triggerType: "form_submission" and point it at your middleware. Use the filter parameter to target a specific form by name.
3. In your middleware, receive the payload and POST to the Discord Execute Webhook endpoint with at least one of content, embeds, components, file, or poll.

A Discord embed payload for a submission looks like this:

{
  "embeds": [{
    "title": "New Form Submission",
    "description": "Name: John Doe\nEmail: john@example.com"
  }]
}

The same pattern works for CMS events using triggers like collection_item_created, collection_item_changed, and collection_item_published, and for publish announcements using site_publish.

Update Webflow CMS from a Discord slash command

This flow runs in the opposite direction and is the one case where you need a Discord bot. A user runs a slash command in Discord, your bot receives the interaction, and your backend updates a CMS item. Use this when community input should write back to your site content.

To implement this:

1. Register a global slash command with POST /applications/{application.id}/commands using your Bot token.
2. Receive the interaction payload at your registered interactions endpoint and parse the command parameters.
3. Call PATCH /v2/collections/{collection_id}/items with your update payload, a Bearer token, and the CMS:write scope, then respond to the Discord interaction to confirm.

Keep Discord's payload constraints in mind: content caps at 2,000 characters and a message supports up to 10 embeds. A single server allows a maximum of 50 integrations combining webhooks and bots.

What can you build with the Discord Webflow integration?

With Discord connected to your site, you can route site activity into community channels and surface community activity on your site without manual checking or copy-paste.

• Form-to-channel alerts: Pipe form submissions into a private #moderator channel so a community manager reviews each application and generates an invite link in real time.
• CMS update notifications: Post a formatted message to an announcement channel whenever a new blog post or resource publishes in your Collection List, so members see fresh content as it goes live.
• Order notifications: Send each new e-commerce order to a #sales-wins channel as a rich embed showing the product and customer details.
• Embedded community widget: Add a Discord server widget to a guild or course landing page so visitors see online members and join a recruitment channel without a separate invite.

If you need more control over payload formatting or two-way CMS sync, take the API path for full flexibility.