How do I build a Discord workflow?
Build Discord workflows with typed conditions, actions, delays, and event waits.
How do I build a draft?
Open Automations on a desktop, choose a Discord event, and add steps. Connect steps on the canvas or choose their next steps in the configuration dialog. Conditions and variables show the types available at that point in the workflow. Unavailable event sources explain which access Yuna is missing.
How do I test and publish a workflow?
Saving updates the draft only. Simulation evaluates your draft without changing Discord and stops when it needs a real action result. Publishing validates the draft and enables an immutable version for new runs. Each existing run keeps the version it started with, including after a delay or retry. A live test performs real Discord actions on the published version and requires explicit confirmation.
How do delays and event waits work?
Delay resumes after a set time. Wait for event resumes when a matching event arrives, or follows its timeout path. Correlate the event to a value from this run, such as the member or channel. Automation-owned buttons, selects, and forms can collect one response for the run that created them. Saved waits and checkpoints survive worker restarts.
How do I manage published workflows?
Disabling stops new runs while existing runs continue. Archive stops new runs and requests cancellation of existing runs; completed Discord actions remain. Duplicate and import create drafts. Version history lets you copy an earlier version into your draft for review and publication. Mobile and tablet views support run inspection and operational controls; building the graph requires a desktop.
How do I inspect and recover a run?
Run history shows the pinned version, executed path, resolved inputs, outputs, and failures. Retry resumes at a failed step and preserves earlier successful steps. Replay starts a new run on the current published version and can repeat actions. If Discord may have accepted an action but Yuna could not confirm its result, the run pauses as uncertain. Check Discord and supply the verified result before resuming.
How do I choose who can automate?
Staff Access separates viewing, draft management, simulation, and publication. Publishing and each action check the publisher’s current authority, Discord permissions, resource availability, role hierarchy, and Yuna safety rules. Automations cannot run arbitrary scripts or make arbitrary HTTP requests.