Skip to content
OrqLabs
Türkçe'ye geç: ENTR

Messaging

Discord bot integration: server announcements and a community assistant

Connect the bot you created in the Discord Developer Portal with its token and Application ID. Your workflows post announcements and summaries to server channels, and interactions sent to the Interactions Endpoint become Inbox conversations.

Start freeStep-by-step setup guide
Connection type
Token
Scope
Per project: every brand connects its own account
Inbound webhook
Yes, you get a webhook URL for incoming events
Capabilities
send messages, receive messages, broadcast
Setup time
20 min

What it does in OrqLabs

The Discord integration links the server where you run your community to OrqLabs workflows. The most common use is announcements: a new blog post, a campaign, release notes or a weekly summary is posted under the bot's name to whichever channel ID you give the Send message node. The connection is per project, so each brand can use its own bot.

On the incoming side, OrqLabs receives the interactions Discord sends to your Interactions Endpoint URL – slash commands and button or menu selections – verifies their signature with your Public Key and opens each one as an Inbox conversation. Like any channel, these conversations can run the AI Chatbot or a workflow with a Message received trigger, and the reply goes to the channel the interaction came from.

Discord messages are limited to 2,000 characters and OrqLabs cuts longer text off at that limit, so keep announcements and summaries short or send them in parts.

What you can automate

  • Server announcements

    In a scheduled workflow, run an announcement drafted by the Content Creator through an approval step and post it to your announcements channel with the Send message node.

  • Reports and release summaries

    Forward the Report Writer's weekly summary or a platform event such as post.published to your team's Discord channel.

  • Interactions in the Inbox

    Slash-command and button interactions sent to the Interactions Endpoint open as Inbox conversations; the AI Chatbot can answer from your knowledge base or your team can take over.

  • Media and link sharing

    Give the Send message node a media URL and images are posted as embeds, other files as links.

Agents that work with it

Nodes that use this integration

In the workflow editor these nodes run with your Discord Bot account.

  • Message received

    Starts when a customer message arrives on a connected channel like WhatsApp or Telegram; e.g. so your chatbot answers automatically.

  • Send message

    Sends a message to one person on WhatsApp, Telegram, SMS and more, e.g. delivering a chatbot reply or an appointment reminder.

  • Hand off to human

    Passes the chat to someone on your team, silences the bot in that chat and alerts the team, e.g. when a customer complains or asks for a person.

Setup at a glance

  1. Create an app with New Application in the Developer Portal and copy the Application ID and Public Key from General Information.

  2. On the Bot tab, use Reset Token to get the bot token and turn on Message Content Intent.

  3. In OAuth2 → URL Generator, select the bot and applications.commands scopes and the bot permissions, then open the generated URL to add the bot to your server.

  4. In OrqLabs, go to Integrations → Discord Bot → Connect, pick the project and fill in Bot Token, Application ID and Public Key.

  5. For incoming interactions, paste the webhook URL from the card into Interactions Endpoint URL in the Developer Portal and save – Discord checks it with a PING.

  6. Turn on Developer Mode in Discord, right-click a channel to copy its ID and use it as the recipient in the Send message node.

Read the full setup guide →

Requirements

  • Manage Server permission on the server and a Discord Developer Portal account.
  • An application with a bot in the Developer Portal: the Bot Token, the Application ID and, for incoming interactions, the Public Key.
  • The bot invited with the bot and applications.commands scopes and the View Channels, Send Messages and Read Message History permissions.
  • Channel role permissions that let the bot post where it should write.

What you enter when connecting

  • Bot Token *
  • Application ID *
  • Public Key (interactions)

Good to know

  • Discord delivers ordinary channel messages over its Gateway connection, not over HTTP webhooks. OrqLabs receives Discord input through the Interactions Endpoint; if the bot needs to listen to every message in a channel, confirm the setup with your platform admin.
  • Messages are capped at 2,000 characters; longer text is cut off.
  • There are no Discord DM campaigns – announcements are posted as channel messages. To DM a user, they must share a server with the bot.
  • Once a bot is in more than 100 servers, Discord requires verification; a single company server doesn't need it.

Frequently asked questions

Can the Discord bot post to an announcements channel automatically?

Yes. In the Send message node, choose Discord as the channel and the channel ID as the recipient; the bot needs the Send Messages permission there.

Do I need slash commands?

Not for posting announcements or notifications. If you want server members to send input to OrqLabs, those interactions – commands and buttons – arrive at the Interactions Endpoint.

Can I add the same bot to several servers?

Yes, the same bot can be invited to several servers. When sending, the channel ID decides where the message goes.

Does the Discord connection cost anything?

Discord's bot API is free; on the OrqLabs side, only steps that use AI are metered.

Get started with OrqLabs

Build your first workflow today

Start on the free plan: connect your accounts, pick a template and stay in control with approval steps. No credit card required.

Start freeExplore the product