Flows: build automations without code

A flow is a small routine that yurna runs for you: something happens (the trigger), yurna optionally checks something (logic) and then does something (actions). Use it to build a verification button, a daily reminder, a welcome DM or your own command such as /flow rules – no programming needed.

You'll find flows under Dashboard → Automations → Flows (/dashboard/<server>/flows). Without a Half Moon or Full Moon plan the page shows a preview; creating flows requires a plan.

How to set it up#

1. Open Dashboard → Automations → Flows and click New flow – or Start from a template if you'd like to begin with a ready-made idea.
2. Give the flow a name and click Create. The editor opens.
3. Pick a trigger on the left, for example “Member joined” or “/flow command”. You can click blocks or drag them onto the canvas.
4. Add actions and logic and connect them: from the dot on the right of one block to the dot on the left of the next.
5. Click a block to configure it on the right (text, channel, role …).
6. Save (Ctrl/⌘ + S works too), then start a test run.
7. When everything looks right, switch the toggle at the top to Enabled.

Test runs and runs#

A test run always uses the saved version. Without the Really run it checkbox nothing happens in Discord – yurna only logs what would happen (“Would send message”, “Would change role” …). You can enter test values for command options and pick a channel to act as the “current channel”.

Under Runs (/dashboard/<server>/flows/<flow>/logs) you can see what the flow did recently: status (Success, Error, Running, Waiting), duration and every single step. Errors are written in plain language, such as “Role is above the bot's role” or “DM could not be delivered (DMs closed?)”.

Limits per run#

To keep flows from getting out of hand, fixed limits apply:

• at most 100 steps, and each block runs at most once per run (protection against loops)
• at most 10 messages, 3 DMs, 10 role changes and 3 HTTP requests
• waiting at most 15 minutes in total
• at most 5 runs at the same time per server

Premium#

Every /flow command is a flow itself, so it also counts towards your active flows.

If more flows are enabled than your plan allows (for example after a subscription ends), the ones created first keep running. The newest ones are shown as Paused (plan) in the list. Turn some flows off or move to a bigger plan.

Common problems#

• The flow doesn't start: Is it enabled and does it have a trigger? Otherwise the list shows “No trigger” or “Paused (plan)”.
• “Reply” is marked as an error: Reply only works after “/flow command”, “Button clicked” or “Message contains”. Use “Send message” otherwise.
• A role isn't assigned: yurna never assigns roles with admin or other dangerous permissions, managed roles, @everyone or roles above its own bot role.
• Your old custom commands are gone: They were converted into flows automatically and now run through /flow.

See also#

• Triggers and blocks
• The /flow command
• Templates and shared flows
• Plans compared