Automations

Automations

Build visual workflows that react to events, compose templates, and pass custom variables.

Automations are visual workflows that run when something happens in your server. Wire triggers, value nodes, and actions into a graph — a trigger starts the run, value nodes prepare data, and actions send messages or perform work.

In this section

Build your first automation

Add exactly one trigger — the event that starts the run, such as Message Created, Member Joined, or Ticket Created.

Add one or more action nodes below it. A simple first automation is often just Send Template wired to the trigger.

Feed the action the data it needs. Wire a channel into Send Template, or wire a dictionary into a Variables input.

Save the draft, then Publish. Drafts do not run until the published version is updated.

An automation can only have one trigger. Assistance validates structure, missing inputs, type mismatches, loops, and step-budget problems when you publish.

Demo flow

The example below shows a realistic pattern:

  • Message Created starts the run
  • Two text literals fill a dictionary
  • Compose Template uses both ${metadata.*} and built-in variables
  • Send Template posts the result back to the same channel
Automation mini map

This example listens for a new message, builds a small dictionary, composes a template with ${metadata.*} placeholders, and sends the result back to the same channel.

Drafts and publishing

Automations have a draft/publish split:

  • Save draft stores your in-progress graph
  • Publish updates the live version that the bot actually runs

If publish fails, Assistance points to the problematic node and explains what is missing or invalid. See Publishing for a walkthrough, or the validation reference for every error code and limit.

Reference

How is this guide?

On this page