Flow reference: Triggers
Slash Command
Runs when a user invokes a slash command.
Runs when a user invokes a slash command.
When and how to use it
Add this trigger to the appropriate flow; it has no incoming execution connection.
Configure its filters and identifiers below.
Connect an output to the action that should respond to this event.
Configuration fields
Slash command — name
The name used by this action. Command names, variable keys and channel names follow different rules; read the block purpose before reusing a name.
Input: Text.
Format example, not a ready value for your server:
ban.Default:
command.Slash only (no prefix version) — noPrefix
Enable to keep this command slash-only even when the bot has text prefixes configured.
Input: On/off switch.
Editor guidance: When the bot has prefixes (Commands page), !name also runs this command. Turn on to allow only /name.
Description — description
Explain this command, role, product or giveaway in terms of its result. Do not put credentials here.
Input: Multiline text.
Format example, not a ready value for your server:
Ban a member from the server..Default:
A Bottly command.Where it can be used — scope
Select where the command or limiter applies. The same label can mean a command context or a cooldown scope; use the choices offered by this block.
Input: Fixed choice.
Editor guidance: Automatic: only in servers when a block needs one (roles, channels, members), otherwise also in DMs with the bot.
Available choices (preserve the exact value):
`` — Automatic
guild — Servers onlyeverywhere — Servers and DMs with the botOnly for members who can… — memberPermission
Default member permission for command availability. Also check sensitive actions inside the flow.
Input: Fixed choice.
Editor guidance: Hides the command from everyone else. Server admins can still change this in Server Settings → Integrations.
Available choices (preserve the exact value):
`` — Everyone
Administrator — AdministratorManageGuild — Manage ServerManageRoles — Manage RolesManageChannels — Manage ChannelsManageMessages — Manage MessagesKickMembers — Kick MembersBanMembers — Ban MembersModerateMembers — Timeout MembersManageNicknames — Manage NicknamesManageEvents — Manage EventsManageThreads — Manage ThreadsViewAuditLog — View Audit LogMentionEveryone — Mention @everyoneManageWebhooks — Manage WebhooksCommand options
Add inputs in the options editor, choose the correct types, and place required inputs before optional ones. Option names are how later blocks read their values. [Command guide](/docs/commands).
Outputs and next steps
out: Continue to the next step.Test and troubleshoot
Invoke the correct trigger with simple inputs and verify the expected effect. Confirm variables exist on this path. A preview alone does not verify Discord delivery.
Save, validate and publish. Perform one real test and read the first relevant log error. [Testing](/docs/flow-testing) · [Variables](/docs/flow-variables) · [Permissions](/docs/flow-permissions).
Save, validate and publish. Perform one real test and read the first relevant log error. [Testing](/docs/flow-testing) · [Variables](/docs/flow-variables) · [Permissions](/docs/flow-permissions).