Server and moderation nodes
Create channels and roles, manage permissions, and apply moderation actions from a graph.
These nodes need a server context. Use server commands or server events. BotDen uses saved actions to prepare the permission request in its generated invite automatically; the tables below are a reference for troubleshooting. A permission requirement on the command controls who may invoke it; the bot's own permissions control what it can do.
Channels
| Node | Inputs | Permission |
|---|---|---|
| Create Channel | Name, channel type, optional parent category/topic, output name | Manage Channels |
| Delete Channel | Channel ID or variable, optional reason | Manage Channels |
| List Channels | Output name and any available filter | Access to the server |
Use a category ID for a parent. A newly created channel's ID can be stored under the chosen output name for later nodes. Use a server setting for an existing channel that differs between servers.
Delete Channel removes the channel and its messages. Restrict the command and use an explicit target. For support requests, Ticket System provides a panel and private-channel setup.
Roles
Create Role accepts a name, color, permissions, visibility options, and an output name for the new role ID. List Roles makes role details available to the flow under its output name.
Manage Role selects an action (add, remove, or toggle), a role, and a target member. Use {user.id} for the command user or {option:member} for a declared user option. Add Role and Remove Role provide the corresponding shortcuts.
If an assignment fails, check role order and permissions. Managed integration roles cannot be assigned like ordinary roles.
Set Permissions
Choose the channel, target type (role or user), target ID, and permissions to allow or deny. This sets a channel-specific permission overwrite. Check the channel with the target member's access before relying on it for a private workflow.
For a role menu, connect a button or select branch to Manage Role. Do not expose roles with moderation or server-management powers as unrestricted self-service options.
Moderation
| Node | Inputs | Bot permission |
|---|---|---|
| Kick Member | Member and optional reason | Kick Members |
| Ban Member | Member, optional reason, optional message deletion window | Ban Members |
| Timeout Member | Member, duration in seconds, optional reason | Moderate Members |
Select the target from a user command option when a moderator is choosing another member. Discord role hierarchy still applies: the bot cannot moderate the server owner or members above its role.
For an automated infraction policy, use Adjust AutoMod Infractions and configure the module's threshold action.