Flow reference: Server Management
Create Private Channel
Create a channel only chosen members and roles (and the bot) can see, e.g. a ticket. Sets {privateChannel}, {privateChannel.id} and {privateChannel.name}.
Create a channel only chosen members and roles (and the bot) can see, e.g. a ticket. Sets {privateChannel}, {privateChannel.id} and {privateChannel.name}.
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
Channel 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:
ticket-{user.username}.Category (id or name) — parent
Parent category ID in the same server. Creating a child does not automatically give every member access.
Input: Text.
Default: ``.
Type — channelType
Choose the channel type before entering its other properties. Text, voice and category channels support different fields.
Input: Fixed choice.
Default:
text.Available choices (preserve the exact value):
text — Textvoice — VoiceMembers who can see it (one per line) — members
Members who get access, one per line: mentions, IDs or {variables} such as {user.id}. Members that cannot be found are skipped.
Input: Multiline text.
Format example, not a ready value for your server:
{user.id}.Default:
{user.id}.Roles who can see it (one per line) — roles
Roles that get access, one per line: role mentions, IDs or exact role names. Roles that cannot be found are skipped.
Input: Multiline text.
Format example, not a ready value for your server:
Support.Default: ``.
Topic — topic
Topic displayed for the channel. Do not put private operational notes into a topic visible to members.
Input: Text with variable suggestions.
Default: ``.
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:
privateChannel.Outputs and next steps
out: Continue to the next step.failed: The operation failed; provide a safe error response.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).
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).