Automations
Trigger actions automatically when your data changes.
What are automations?
Automations follow a simple shape: When something happens, If optional conditions are met, Do one or more actions. They run in real time and every run is logged.
Examples:
Triggers, conditions, and actions
A trigger is the event that starts the automation. Conditions gate what happens next, and actions are what the automation does.
| Triggers | Actions |
|---|---|
| Record created | Update record |
| Record updated | Create record |
| Field value changed | Send email |
| Form submitted | Send notification |
| On a schedule | Call a webhook |
| Request approval |
Conditions can be split into branches: an If branch, any number of Else if branches, and an optional catch-all branch. Each branch runs its own set of actions, so one automation can handle several outcomes.
Update-record actions can target the triggering record, a linked record, or every record that matches a filter (find all). That last one is handy for bulk updates like "mark all overdue tasks as At Risk".
Managing automations
Access automations from the sidebar under your base. Related automations can be grouped into workflows with a shared name, icon, and color. Each automation shows:
You can pause, edit, duplicate, or delete automations, and open the run history to see exactly what each run did.
Automations that create or update records can trigger other automations. SAJEL caps how deep these chains can go and limits runs per workspace, but it's still best to design carefully.