Discord

Communication Webhook URL, or a bot token Windmill docs

Post messages, read a channel, open forum threads and answer slash commands from any Windmill script, flow or app. A webhook URL is enough to post; a bot token does the rest.

What you can do with Discord

Complete, deployable projects built around Discord — the fastest way to get something real running.

Set up in 3 steps

1

Create a webhook in your server

In Discord, open Server Settings, then Integrations, then Webhooks. Create one, pick the channel it posts to, and copy its URL.

2

Add the resource in Windmill

Open Resources, add a resource of type discord_webhook, and paste the URL.

3

Run your first script

Fork the send message script below, or set the error handler script as a flow's failure step to get alerts in the channel.

Scripts

Building blocks, if none of the projects above fit. Fork one, run it, or call it as a step inside your own flow.

Flows

Multi-step workflows that already wire Discord to something else.

All flows →

Trigger flows from Discord

Discord is not only a destination. These inbound paths are supported today.

Slash commands

Type a command in Discord and it starts a flow, with what you typed as its inputs.

All resource types

Questions

Webhook or bot?

A webhook only posts to the one channel it was created for, and needs no application — that covers alerts and reports. Create a Discord application and use the discord_bot_configuration resource when a script must read messages, manage threads, or answer interactions.

Where do the bot fields come from?

Create an application at discord.com/developers/applications. bot_token is on the Bot tab; application_id and public_key are on General Information.

Is my webhook URL stored on the hub?

Never. It lives only in your own Windmill workspace, encrypted at rest — and anyone holding that URL can post to the channel.