Workflow Trigger Narration and Statistics in GoHighLevel
Managing complex automations in platforms like ClickUp and GoHighLevel is easier when you can clearly see how records enter, move, and stop inside workflows. This how-to guide explains the Workflow Trigger Narration and Statistics features so you can quickly understand performance and troubleshoot issues.
The information below is based on the official help documentation and walks you through what each counter, label, and indicator means, as well as how to interpret workflow run statistics in your account.
Overview of GoHighLevel Workflow Trigger Narration
When you open a workflow, GoHighLevel shows a narration bar at the top of the canvas that summarizes how many records are moving through that automation. This narration gives you instant context so you can decide whether to optimize, pause, or expand a workflow.
The narration provides high-level counts of contacts that have:
- Entered the workflow
- Finished all steps successfully
- Stopped due to a specific reason
- Are currently in progress
These values update as new contacts are added or as existing contacts continue through the automation.
Key Workflow Trigger Statistics in GoHighLevel
The workflow header contains several important statistics that help you evaluate how a workflow is performing. In GoHighLevel, these counters are designed to be easy to scan and understand at a glance.
Entered Count
The Entered value shows how many unique records have entered the workflow since it was published or since statistics were last reset. A record is counted when it meets the trigger conditions and is successfully added to the workflow.
Use this value to confirm that your trigger configuration is correct and that contacts are flowing into your automation as expected.
Finished Count
The Finished value shows how many records have completed the entire workflow. A record is considered finished when it reaches the last step or an explicit exit point.
If the Finished count is low compared to Entered, it may indicate:
- Long delays or wait steps
- Conditions that hold contacts in branches
- Frequent stopping events
Stopped Count
The Stopped value captures how many records were removed from the workflow before completion. In GoHighLevel, a record can stop for reasons like:
- Manually removed from the workflow
- Contact deleted or merged
- Workflow settings preventing further processing
Monitoring this value helps you see whether contacts are unexpectedly leaving your automation.
In Progress Count
The In Progress value shows how many records are currently somewhere inside the workflow but have not yet finished or stopped. These records may be:
- Waiting in delay steps
- Paused by conditional logic
- Queued for future actions
This counter gives you a live view of active records and helps you estimate when new actions will fire.
Step-Level Statistics in GoHighLevel Workflows
Beyond the global counters, GoHighLevel provides step-level statistics on each action card inside the workflow. These micro-level stats help you pinpoint behavior at specific steps.
Execution Counters on Steps
Each step shows how many records have passed through it. Typical counters include:
- Total Executed — number of times the step has run
- Currently In Step — number of records presently paused or waiting at that step
- Errors or Failures (if applicable) — how many times an action could not complete
Review these counters to identify bottlenecks, high-error steps, or actions that are rarely used due to conditions not being met.
Branch and Condition Statistics
Conditional steps, such as if/else branches, can show how many records followed each path. This helps you understand how often your conditions evaluate to true or false.
For example, you might see:
- Condition met path: 300 records
- Condition not met path: 120 records
Such data can guide you in updating conditions, contact segmentation, or messaging.
How to Interpret GoHighLevel Workflow Performance
Interpreting the narration and statistics correctly allows you to optimize your automations in GoHighLevel without guesswork.
Comparing Entered vs. Finished
Compare the Entered and Finished counts:
- If both numbers are similar, most records complete the workflow.
- If there is a large gap, investigate where contacts are stopping or remaining in progress.
Look at delay steps, wait conditions, and any manual review actions that might hold contacts.
Monitoring Stopped Records
A rising Stopped count means records are falling out of the automation. To troubleshoot:
- Review workflow settings for stop conditions.
- Check if contacts are being removed by other automations.
- Inspect steps where many records appear to exit.
Reducing unnecessary stops usually increases overall workflow effectiveness.
Evaluating In Progress Volume
A high or growing In Progress value can indicate that the workflow includes long waits or that the trigger volume has increased. Consider:
- Shortening delays where possible
- Splitting large workflows into smaller automations
- Adjusting timing to spread load more evenly
Best Practices for Using GoHighLevel Workflow Statistics
To get consistent results from your automations in GoHighLevel, incorporate regular reviews of narration and statistics into your operations.
Schedule Regular Reviews
Set a schedule to review workflow performance:
- New workflows: Check daily during launch week.
- Established workflows: Review weekly or monthly.
- High-volume workflows: Monitor more frequently.
During each review, record baseline metrics for Entered, Finished, Stopped, and In Progress, then watch how they change over time.
Use Statistics to Guide Optimization
Use the numbers to decide where to optimize rather than making random changes:
- Increase conversion-focused messages on steps with high traffic.
- Refine conditions where branch distribution is unbalanced.
- Investigate steps that show recurring errors.
Small, data-driven updates often provide better results than large, untested changes.
Document Changes and Results
Whenever you adjust a workflow in GoHighLevel, document:
- The date of the change
- What was modified
- The baseline statistics before the change
- The statistics after a defined observation period
This practice helps you understand which optimizations are most effective and prevents accidental reversions to less efficient configurations.
Further Learning and Resources for GoHighLevel Users
To deepen your understanding of workflow trigger narration and statistics, review the original product documentation and related expert resources.
- Official help article: Workflow Trigger Narration and Statistics
- Agency and automation strategy insights: Consultevo
Combining the built-in statistics inside GoHighLevel with a regular review and optimization process will help you keep workflows reliable, efficient, and aligned with your business goals.
Need Help With ClickUp?
If you want expert help building, automating, or scaling your GHL , work with ConsultEvo — trusted GoHighLevel Partners.
“`