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 and choose a blank workflow, a multi-step recipe, or the dedicated Yuna system for a common task. Click a step to configure it, then use its branch buttons to add or insert the next step. Arrange tidies the canvas without changing its logic. 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 creates an immutable version. Paused automations stay paused unless you choose to enable them in the publish dialog. Each existing run keeps the version it started with, including after a delay or retry. Fill in example event fields to simulate a draft; event JSON is available under Advanced. A live test performs real Discord actions on the published version and requires explicit confirmation. You can publish while paused to test without accepting new events.
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.
What should I know about stored values and repeated events?
Persistent variables are stored per server, member, or channel and can be inspected from their own tab. Publishing access is required to create, edit, or delete a live value. A workflow can also keep a value for just one run. Trigger cooldowns skip repeated matching Discord events for a chosen member, channel, or server. A missing member or channel cannot satisfy that cooldown scope.
What should I know about run on demand?
Choose Run manually when you want an administrator to start the workflow. After publishing, use Run now from the automation list and confirm its real Discord actions. The starting member is the administrator who starts it. Manual runs and live tests remain pinned to a published version.
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.