- Documentation
- Automations
- The /flow command: custom commands for your server
The /flow command: custom commands for your server
With /flow, members start your flows as a slash command – with a name, optional text input and a member.
Requires Premium
This feature is available from the Half Moon plan.In yurna you build custom commands as a flow with the /flow command trigger. Members start it through the single /flow command and pick the name there – for example /flow name:rules. The command only works on the server the flow belongs to.
In the dashboard#
The old Custom commands page now leads straight to Flows – every custom command is a flow.
- Create a flow under Dashboard → Content & automations → Flows (or use a template such as “/rules with embed”).
- Drag the /flow command trigger onto the canvas and click it.
- Enter the /flow command name: lowercase letters, digits and hyphens only, up to 32 characters, unique per server.
- Write a short Description (up to 100 characters). It appears in Discord in the
/flowpicker. - Optionally set a Cooldown (seconds) – how long each member has to wait before starting the flow again (0 = none, at most one day).
- Connect actions such as Reply, save and enable the flow.
Using inputs#
/flow has two fixed, optional fields:
- input – free text (up to 1000 characters), available in the flow as
{option.eingabe} - member – a member, available as
{option.mitglied}(mention),{option.mitglied.id}and{option.mitglied.name}
On top of that there's {count} (how often the command has been used) and all general placeholders such as {user}. In “Send DM” and “Add/remove role” you can choose Member from a command option as the target – the action then affects the given member instead of the person using the command.
By command#
| Command | What it does | Key options | Who can use it |
|---|---|---|---|
/flow <name> [input] [member] | starts an enabled flow with the “/flow command” trigger | name: which flow command, input: free text, member: a member | all members (can be restricted in the flow) |
/server flow list | shows every flow with its state | – | Manage Server |
/server flow enable <flow> | turns a flow on | flow: which flow | Manage Server |
/server flow disable <flow> | turns a flow off | flow: which flow | Manage Server |
The /flow name list only suggests enabled flows that fit your plan. New /flow commands are created in the dashboard only.
Tip
Want only certain roles to use the command? Add a Condition → Member has role right after the trigger and connect only the Yes output to your actions.
Premium#
| New Moon | Half Moon | Full Moon | |
|---|---|---|---|
| /flow commands | – | 10 | 50 |
| Active flows in total | – | 5 | 50 |
Because every /flow command is its own flow, on Half Moon the number of active flows also limits how many /flow commands you can use.
Common questions#
What does “is paused right now” mean?#
The flow is disabled or above your plan's limit. Turn it on in the dashboard or with /server flow enable.
What does “There is no flow command … on this server” mean?#
The name is misspelled or belongs to another server. It's best to pick the command from the list.
What does “Please wait … s” mean?#
The cooldown is still running. You set it on the /flow command trigger.
Why does an old custom command only reply with a notice?#
Former custom slash commands now run through /flow. The notice tells you the new call, e.g. /flow name:rules.
See also#
Last updated on 30 October 2026