Discord Connect

Overview

Discord doesn’t go through the Connections OAuth flow. Instead, you create an Incoming Webhook for the channel you want to post to, and paste that webhook URL into the Discord node’s configuration inside a workflow. Sending is an external write and pauses for approval before the message actually posts.

This is a send-only integration today — there’s no node to read messages back from a Discord channel.

1. Create a webhook in Discord

In Discord: Server Settings -> Integrations -> Webhooks -> New Webhook. Pick the channel you want messages to land in, then Copy Webhook URL. Keep this URL private — anyone with it can post to that channel.

2. Add a Discord node to a workflow

In Workflow Studio, add the Discord: Send message node and paste the webhook URL into its configuration. The node supports:

• content — the message text
• username / avatar_url — optional overrides for how the message appears
• embeds — structured embed blocks
• thread_id — post into an existing thread instead of the channel root
• allowed_mentions — control which @mentions actually notify people

The webhook is stored per-workflow, not as a shared org-wide credential — if you want the same channel used by multiple workflows, reuse the same URL in each one.

3. Approve the send

Because posting to Discord is an external write, the step pauses for review before it’s delivered — the same approval boundary used for Slack and Notion writes.

FAQ

Do I need to connect a Discord account?

No OAuth step. Discord uses a channel webhook URL you create yourself in Discord and paste into the workflow node.

Can Schift read messages from my Discord server?

Not today. The Discord integration currently supports sending messages only.

What if the webhook URL leaks?

Delete it from Discord’s Integrations settings and create a new one, then update the workflow node with the new URL.