Automations/Automations

Automations

Event rules that react when something happens — forms, records, and host actions.

Automations

Automations are event rules: when something happens in the workspace, the host runs an ordered set of actions. They are not a schedule, not an artifact in the library, and not a general Zapier clone.

Where in the product

Where in the product

Rail browser next to Routines (under the Work family). Create a rule, edit the flow in the panel, and watch runs there.

Automations railAutomations browserCreate automation dialogAutomation panel

How to use it

  1. Create an automation — new rules start paused.
  2. Choose a trigger: form submitted, record created, or record updated.
  3. Optionally add conditions so only matching events run the flow.
  4. Build an ordered flow of host actions (set fields, create or update a record, outbound webhook, or materialize a task / blueprint).
  5. Activate when you want events to fire the rule.
  6. Open the panel for run history and edits.

When judgment needs an agent, use a Work bridge action to materialize a task or blueprint — always a new Work instance per event.

Key distinctions

  • Routines = time (what will fire later on a schedule). Automations = events (something happened). Work = present (what is running).
  • Born paused; activation is intentional.
  • Deleting an automation is permanent (no trash) — recreate if you need it again.
  • Action set is closed product nouns above — not arbitrary code or a node graph.