Automations Overview
Automations allow you to trigger actions in response to CRM events — without writing code. Each automation is a rule: when this happens → do this.
How automations work
An automation has three parts:
- Trigger — the event that starts the automation
- Conditions (optional) — filters that must pass before actions run
- Actions — one or more things that happen when triggered
Automations are scoped to your tenant (id_company) and only fire for records belonging to your account.
Key tables
| Table | Purpose |
|---|---|
automations |
Automation definitions (name, trigger type, active flag) |
automation_conditions |
Filter rules attached to an automation |
automation_actions |
Ordered list of actions to execute |
automation_logs |
Execution history with status and error details |
Execution model
- Automations run asynchronously — they do not block the event that triggered them
- Actions within one automation run sequentially in
sort_order - If an action fails, subsequent actions in the same run are skipped and the failure is written to
automation_logs - An automation can be paused by setting
active = false— it will not fire until re-enabled
Limits
| Limit | Value |
|---|---|
| Automations per tenant | 100 |
| Actions per automation | 20 |
| Conditions per automation | 15 |
| Max execution time | 30 seconds |