With Automation Analytics you can see at a glance how your automations are performing, how much time they're saving you, and where there are problems.
Key Metrics
At the top you'll see three important metrics for the selected time period:
Completed Runs
Number of automation runs where something was actually automated.
What counts as a completed run?
What counts as a completed run?
A run only counts when at least one action node was executed.
Counts:
Trigger → Filter matches → Send message ✓
Trigger → AI agent responds ✓
Trigger → Update label ✓
Doesn't count:
Trigger → Filter doesn't match → Automation stops ✗
Trigger → Condition not met → Automation stops ✗
Example: Your automation has the trigger "New incoming message" + a message content filter that checks for "Help". In the time period, 10,000 messages come in, but only 50 contain "Help". Result: 50 completed runs - not 10,000.
Automated Tasks
Number of tasks executed across all runs. Each executed logic node (filter, condition, wait, etc.) and action node (send message, update label, etc.) counts as one task.
What counts as an automated task?
What counts as an automated task?
Tasks are only counted for runs that also count as "Executed Runs" - meaning runs where at least one action node was executed.
Example:
Automation with 3 nodes: Trigger → Filter → Send Message
100 runs where the filter matches → 2 tasks each (Filter + Send Message) = 200 tasks
500 runs where the filter doesn't match → 0 tasks (don't count as executed runs)
Result: 200 automated tasks
Special case AI Agent:
The AI Agent is a special node. In the Automation Builder you only see one node, but the AI Agent executes multiple actions in sequence - each action counts as a separate task.
AI Agent sends a message → 1 task
AI Agent creates a note → 1 task
AI Agent updates a label → 1 task
Example: The AI Agent has a conversation with 5 messages and creates a note at the end = 6 tasks (even though there's only 1 AI Agent node in the builder)
Time Saved
Total time you've saved through all successfully executed tasks.
How is time savings calculated?
How is time savings calculated?
Each node type has a predefined time value:
Action Nodes: 8 seconds
Message Nodes: 25 seconds
Logic Nodes: 2 seconds
When a node executes successfully, its time value is added to the total.
Time Saved = Sum of all time values for successfully executed nodes within the selected date range.
Which nodes count as Message Nodes: Send Message, Send WhatsApp Template, Send WhatsApp Quick Response, Send WhatsApp List, Send Live Chat Message, Create Note, Ask Question
Example:
Automation with: Filter → Send Message → Update Label
Filter (Logic): 2 seconds
Send Message (Message): 25 seconds
Update Label (Action): 8 seconds
Per run: 35 seconds saved
100 successful runs = 3,500 seconds (approx. 58 minutes) time saved
Special case AI Agent:
Time saved for the AI Agent depends on the type of action it performs:
AI Agent sends message or creates note → 25 seconds (Message Node)
AI Agent updates contact, label, etc. → 8 seconds (Action Node)
Example: AI Agent sends 5 messages (5 × 25 sec.) + creates note (25 sec.) + updates label (8 sec.) = 158 seconds time saved per run
Charts
Runs
Bar chart showing the number of automation runs over time. This helps you spot trends - are your automations running more or less than before?
Runs by Status
Stacked bar chart that breaks down runs by status:
Blue (Running): Still in progress
Green (Completed): Successfully finished
Yellow (Canceled): Manually canceled or canceled by another automation
Red (Failed): Error occurred
Tip: Lots of yellow or red portions? Check the overview table below to see which automations have a low success rate. Then open the affected automation, go to the activity log, filter by status "Failed" or "Canceled" and investigate the cause. Learn more in the article "Debugging automations and fixing errors".
Tasks
Bar chart showing the number of executed tasks over time.
Time Savings
Bar chart showing time saved over time.
Overview table
Below the charts you'll find a table with all automations. Perfect for comparisons - sort by most runs, highest time savings, or lowest success rate to quickly see which automations are performing best or having problems.
Column | Meaning |
Automation | Name of the automation |
Runs | How often the automation was executed |
Tasks | How many tasks were automated |
Time Savings | Estimated time saved |
Success Rate | Percentage of runs without a failed node |
