Automations: overview
Automations put your CRM to work on its own. Each automation follows a simple three-block logic:
Trigger → Conditions → Actions
That is: when something happens (an opportunity enters a stage, a conversation is closed, a tag is added...), if the conditions you defined are met, the platform runs one or more actions — moving cards, tagging, sending messages, creating tasks and much more.
The area lives under the Automations menu, inside the CRM group.
PRINT AQUI #1
Automations screen, with the summary at the top, the Automations and Runs tabs, and the automation list with its columns.
The Automations screen
At the top, you see your operation's summary: the number of automations created and the total of runs in the last 7 days.
The screen has two tabs: Automations (the list) and Runs (the history).
The automation list
Use the search and the All / Paused filters to find what you are looking for. For each automation, the table shows:
| Column | What it shows |
|---|---|
| Automation | Name and description |
| When it runs | The trigger that fires the automation (and the pipeline/stage, when defined) |
| Does | How many actions it runs |
| 7 days | How many times it ran in the last 7 days and when the last run was |
| Status | The toggle that activates or pauses the automation |
In each row's three dots ⋯ menu, you can edit, see the runs or delete the automation.
Runs tab
The Runs tab is the complete history: every time an automation is called, it is recorded here. You can filter by automation and by result.
For each run, you see:
- When — date and time;
- Automation — which one ran;
- Trigger — what called it (pipeline › stage, for example);
- Contact · Opportunity — who it ran on;
- Result — what happened. A skipped run, for example, can be expanded to see the reason — such as "conditions did not match";
- Duration — how long it took.
💡 The Runs tab is your best friend when it comes to understanding why an automation "did not work": most of the time it did run, but it was skipped because the conditions did not match for that contact.
PRINT AQUI #2
Runs tab, with the automation and result filters, and the run table with when, trigger, contact, result and duration.
Next steps
- Create your first automation — see Creating an automation;
- Check the full list of triggers, conditions and actions in the Automations reference.