Flow reference: Server Management
Create Invite
Create an invite link and store it.
Create an invite link 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
Channel (blank = current) — channel
Choose the channel this block targets or filters. Use its Discord ID or a supported channel variable. Check channel overrides for the bot.
Input: Text.
Default: ``.
Expires after (seconds, 0 = never) — maxAge
Invite lifetime in the unit shown, typically seconds. Check the editor's handling of zero before creating an unlimited invite.
Input: Number.
Default:
0.Max uses (0 = unlimited) — maxUses
Maximum number of invite uses. Check the meaning of zero if you intend unlimited uses.
Input: Number.
Default:
0.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:
invite.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).
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).