Flow reference: Server Management

Create Role

Create a role and store it.

Create a role and store it.

When and how to use it

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

Role name — 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 with variable suggestions.

Default: New role.


Colour — color


Color in the format shown by the editor, usually six-digit hex such as #5865F2. Color alone does not change permissions.

Input: Color.

Default: #5865F2.


Show separately — hoist


Whether the role is shown separately in the member list. It does not grant moderation permission.

Input: On/off switch.

Default: false.


Mentionable — mentionable


Whether ordinary members can mention the role. This changes mention behavior, not the role's permission set.

Input: On/off switch.

Default: false.


Store as — storeAs


Choose a short result prefix such as result. Later blocks must use this same prefix and run after this block. It is not a Discord channel or a persistent table.

Input: Text.

Default: role.

Outputs and next steps

out: Continue to the next step.

Read the result after this block, using its configured prefix and the fields supported by the selected operation. Do not assume every response has a text or id field.

Test and troubleshoot

Check caller permissions, bot permissions, channel overrides and role hierarchy separately. Test delete/ban/permission changes in a dedicated server rather than against production data.

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).