Flow reference: Discord Components
Role Select
Older block that does nothing on Discord. Add buttons and menus in a Send Message block.
Older block that does nothing on Discord. Add buttons and menus in a Send Message block.
When and how to use it
This is a legacy block retained for existing projects. Do not choose it for new flows. Follow the replacement described above; old standalone component blocks do not send buttons or menus.
This type is unsupported by the flow executor. Its presence in an older project does not mean it works on Discord.
This type is unsupported by the flow executor. Its presence in an older project does not mean it works on Discord.
Connect the input from the preceding step on the path that should perform this operation.
Fill the fields with data available in the trigger's context.
Connect the needed outputs; an unconnected path cannot run later blocks.
Configuration fields
This block has no ordinary catalog configuration fields. If it opens a rules, form or message editor, configure that part in its dedicated editor.
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).