Overview
Automations
Make things happen when something happens: rules for simple if-this-then-that work, flows for branching multi-step work, with run logs, retries and an emergency stop.
On this page
Automations make things happen when something happens: a message arrives, a task is completed, a booking is made, a website goes down, a schedule is reached. You build them as rules for simple “when this, then that” work, or as flows when the work needs branches, timing or outside tools.
- Open
- every member of a workspace that has Automations — there is no separate Automations permission
- Ask Donna steps
- Pro and Enterprise plans
- Stop every automation at once
- Owner only
- Where
- System Engine → Automations (
/system-engine/automations)
What is in Automations#
| Pill | What it holds |
|---|---|
| Overview | Everything running in your workspace: what triggers most, what needs attention, recent activity and the work automations did for you |
| Rules | Your rules, and Templates to start from |
| Flows | Your flows, and Templates to start from |
| Docs | The built-in reference for every trigger and action: the fields it exposes, what it depends on, and examples |
| Settings | Workspace defaults, what the step palette shows, diagnostics, retention and the emergency stop |
Rules and flows#
- Triggersomething happens in Unobits, on a schedule, or at your webhook
- Conditionsonly continue when it matches
- Actionsone or more steps, in order
| Rule | Flow | |
|---|---|---|
| Built in | A fixed tree: When → Only continue when → Then | A canvas: drag steps and connect them |
| Reaches | Unobits only | Unobits and outside tools (webhooks, Google Sheets) |
| Good for | One trigger, a few conditions, a few internal actions | Branches, delays, approvals, reshaping data, calling other systems |
A rule can be converted into a flow when it outgrows the tree. It cannot be converted back. See Rules and flows.
Three ways to start#
- Start from scratch — choose Create rule or Create flow.
- From a template — such as Site down escalation, Meeting text to event or 5pm reminder.
- Describe it — Donna builds it — say what should happen in plain language, for example “When a task is completed, draft a friendly status update and post it to the project chat”. Donna picks the trigger and steps and gives you a draft to review before saving.
Who sees what#
Automations belong to the workspace. Every member can see, create and change them; each automation records who created and last changed it. Only the Owner can pause every automation in the organization at once — see Settings and access.