Discord Actions let workflows interact with your connected Discord server.
They can send messages, manage roles, moderate Discord members, and respond to slash commands.This page explains each Discord action block in detail, including what it does, what it accepts, and what it outputs.
The Send Discord Message block posts a message in the selected Discord channel when the workflow reaches it. It can be used for staff alerts, moderation logs, workflow updates, or automated announcements.
Input
Channel: The Discord channel where the message should be sent. Channels are selected from a searchable channel dropdown.
Content: The message content. This can be manually typed or use output from another block.
Output
Message: The message that was sent. This includes the message ID and channel ID as string values.
A workflow can post to a management channel when a staff member removes someone from a department.Filip removed RadicalVision from the Training Department.
The Respond to Slash Command block sends the response message for the slash command that triggered the workflow. It is used to confirm that a command ran or show the result of the workflow.
Input
Content: The response message shown to the slash command user.
The Add Discord Role block gives the selected Discord user the selected Discord role. It is useful for role syncing, staff onboarding, temporary access, or automated permission changes.
Input
User: The Discord user who should receive the role.
Role: The Discord role that should be added.
Output
No direct output. The workflow continues after the role is added.
The Remove Discord Role block removes the selected Discord role from the selected Discord user. It is useful for removing access when staff roles change, punishments expire, or a user leaves a department.
Input
User: The Discord user who should lose the role.
Role: The Discord role that should be removed.
Output
No direct output. The workflow continues after the role is removed.
The Kick From Discord block removes the selected Discord user from the connected Discord server. The user is removed, but they may be able to rejoin later if they have a valid invite.
Input
User: The Discord user who should be kicked.
Output
No direct output. The workflow continues after the user is kicked.
The Ban From Discord block bans the selected Discord user from the connected Discord server. A banned user is removed from the server and cannot rejoin unless they are unbanned.
Input
User: The Discord user who should be banned.
Output
No direct output. The workflow continues after the user is banned.
Discord actions usually need data from a trigger or an earlier block. For example, a slash command can provide the invoking user, selected channel, command options, or target user.Before using Discord actions, link your Discord server from the Discord Integration module. For setup instructions, see Linking Your Server.When using Discord actions, consider:
Bot Permissions: Make sure the bot can send messages, has Manage Roles when using role actions, and can kick or ban members when using moderation actions.
Role Order: For role actions, the bot’s highest role must be higher than the role it is adding or removing. For kick and ban actions, the bot’s highest role must be higher than the target user’s highest role.
Connected Server: Discord actions require the Discord integration to be connected.
User Feedback: Slash command workflows should normally include an ephemeral response so the command user knows what happened.
