Automation rules: from a sentence to a running rule

From a sentence to a structured rule

In the sentence box you write what to do and when, for example when a cut is approved, notify the editor and create the delivery task. You can also pick one of the suggested ideas for a team and adjust it. Clicking Turn into a rule sends the sentence to the engine that builds it into a trigger (when), conditions (and when, unless) and actions (what to do) - a trigger can be a task moving to another stage, an approval being decided, a comment being added, a file being uploaded, a deadline drawing near, a field changing, a project passing its agreed revision rounds, or a fixed schedule; actions include creating a task, assigning, moving to a stage, notifying, sending an email, setting a field, calling a webhook, starting an AI proposal, waiting, or escalating if still unresolved.

An automation never deletes, removes or revokes a permission. That is a fixed limit of the engine, not a setting you can turn off.

The preview before anything runs

After it compiles, a preview appears titled Here is how we understood it: how many times the rule would have fired last month against events that already happened, concrete examples of those firings, and the compiled rule itself. If something is off, for instance the rule sends over a channel that is not connected yet, the preview warns about it there instead of turning on a rule that cannot work. From there you choose Confirm and enable to turn the rule on, or Keep it disabled to save it without enabling it.

Create a new automation

The process starts with a sentence and ends with an explicit confirmation.

1. On the Automations screen (under More > Automation), write what to do and when in the sentence box, or pick a suggested idea from the list.
2. Click Turn into a rule.
3. Read the preview titled Here is how we understood it: how many times it would have fired, the examples, and any warnings.
4. Click Confirm and enable to turn the rule on, or Keep it disabled to leave it off for now.

Managing an existing automation

Every automation in the list shows an Enabled or Disabled badge, how many times it fired, and when it last fired. An Enable switch turns it on and off, and a separate Dry run switch makes it only log what it would have done without actually doing it, a safe way to test a new rule against real traffic. Show runs opens that rule's own runs log, with the time, the status, which conditions matched and which actions ran. Edit opens a form where you can change the trigger, the conditions or the actions field by field; saving a changed rule leaves it disabled until you turn it on again. Delete removes the rule and its runs log, after you confirm.