Automations

An automation does something on its own when a record changes: when this happens, only if these are true, then do that. Owners and admins manage them in the workspace menu, Integrations, Automations (action core.automations.list).

Writing an Automation

Add an Automation (action core.automations.save):

• When: any event: a record added, changed, or deleted in any module, or an app's own event, such as a ticket opening or a form being sent.
• Only if (optional, up to 10, all must be true): a field of the record and a comparison: is, is not, contains, does not contain, is empty, is not empty, is more than, is less than, changed, or changed to. Text comparisons ignore capital letters. More and less compare numbers, or dates written like 2026-10-07.
• Then (1 to 10 steps, in order):
  • Change a field of the record.
  • Add a record to any module, with values for its fields.
  • Give the record to a person (its owner).
  • Add a note to a record that takes notes, such as an internal note on a Helpdesk ticket.
  • Notify people by email: owners and admins, the record's owner, or one person in the workspace. Notices go only to people in your workspace, say which automation sent them and why, and link to the record.
  • Send a webhook: the event, to one of your webhooks, whatever events that webhook lists itself.
  • Call a connected service: a POST to one of your API connections, at the path you give, with its saved key and the body you write. A body that starts with { or [ is sent as JSON.

In values, messages, and bodies, {{field}} puts in a field of the record by its key (such as {{name}} or {{email}}), {{id}} its number, {{module}} its module, and {{event}} the event. In a JSON body each value is written safely as JSON text.

A new automation is saved turned off, so you can look it over. Turn On (action core.automations.turn_on) checks it against your setup again; Turn Off (action core.automations.turn_off) stops it. Delete (action core.automations.delete) removes it; what it already did stays.

How Automations Run

• An automation runs right after the change that sets it off, as "the automation", with the same record checks as everyone. Its changes are marked Automation in the record's history.
• Its steps go all or nothing: if any step fails, nothing it changed is kept, and the run shows which step failed and why. A failed run is also written in the Activity Log.
• Notices, webhooks, and service calls are queued and sent within moments, then tried again if they fail, like any webhook delivery.
• Changes an automation makes never set off automations, so automations cannot set each other off in a loop. They do reach your webhooks.
• Runs (action core.automations.runs) shows the newest 50 runs, each step's result, and any failure. The list shows how many runs each automation has had, how many failed, and the last failure.

AI Agents

An AI agent you connect (AI Agents) can read your automations and their runs, draft new ones, and turn them off, if you are an owner or admin. Anything it saves is always turned off and marked Drafted by an AI agent, and an agent's change to an automation that is on turns it off. Only a person can turn an automation on.