GoHighLevel Workflow Stats Guide
If you are moving automations from ClickUp task lists into a CRM, understanding how statistics work in GoHighLevel workflows is essential. This guide explains how to read workflow stats so you can troubleshoot issues, improve performance, and gain clear insight into what is happening at every step of your automation.
The information below is based on the official workflow statistics documentation, adapted into a practical, step-by-step how-to article you can use while building and optimizing campaigns.
Where to Find GoHighLevel Workflow Stats
To access workflow statistics in GoHighLevel, you must first open the specific workflow you want to analyze.
- Log in to your account and go to Automations > Workflows.
- Click on the workflow whose stats you want to review.
- Make sure you are in the main workflow builder view, not inside an individual step’s edit screen.
- Locate the counters displayed directly on each action or trigger step in the workflow canvas.
Each workflow step in GoHighLevel displays small numerical counters. These show how many times the step has run, how many contacts are inside, and if any errors occurred.
Understanding GoHighLevel Workflow Step Counters
Every step in your automation includes multiple counters. Learning what each counter means will help you accurately interpret your GoHighLevel workflow behavior.
Executions Counter
The Executions counter shows how many times the step has been executed overall.
- Includes every run, whether it was successful, errored, or currently in progress.
- Represents the total volume of activity that passed through that step.
- Useful for understanding how often a particular action is triggered within the workflow.
If the executions number is high, but your end results are low, you may need to investigate later steps in the GoHighLevel workflow for bottlenecks or errors.
Contacts In Step Counter
The Contacts in step counter shows how many contacts are currently paused or waiting at that step.
- Only counts contacts currently in progress at that exact action.
- Does not include contacts that have already moved past the step.
- Does not include contacts that have finished the workflow entirely.
This counter is especially helpful for timing-based steps such as Wait actions or delays in GoHighLevel when you want to see how many people are queued.
Errors Counter
The Errors counter tracks how many times the step has failed to execute correctly.
- Counts the number of execution errors for that specific step.
- Successful executions are not included in this number.
- In-progress executions are not included in this number.
When you see a non-zero error count, it is a signal to inspect the step’s configuration, connected integrations, or the data being used by that action in GoHighLevel.
How Execution Status Works in GoHighLevel
Each workflow step records one execution per contact every time that contact passes through the step. This means:
- One contact equals one execution for that step, at that time.
- If the same contact re-enters the workflow (due to settings or re-enrollment rules), new executions will be counted.
- Executions are tracked at the step level, not only at the workflow level.
The counters give you a precise way to monitor how individual steps perform over time inside GoHighLevel automations.
What Counts as an Execution
An execution is counted when:
- A contact reaches a step and the system attempts to perform the action.
- The action is successfully completed, or
- The action encounters an error during processing.
Contacts that are still waiting in a step are in progress, but their executions are already counted in the Executions total. The difference is that in-progress contacts are also displayed in the Contacts in step counter, while completed ones are not.
Checking GoHighLevel Workflow Stats for Troubleshooting
The stats panel in GoHighLevel can quickly show you where issues are happening in your automation.
Step-by-Step Troubleshooting Process
- Identify unusual error counts
Scan each workflow step for a high number in the Errors counter relative to the Executions. Focus on steps where errors represent a meaningful portion of total executions.
- Compare executions to contacts in step
If many contacts are stuck at a step (high Contacts in step) but the workflow is not progressing, check whether the action requires a condition to be met (for example, a time delay or filter).
- Inspect the step configuration
Open the step and verify all required fields, tags, conditions, and integration settings. In GoHighLevel, errors often come from incomplete configurations or missing external data.
- Review related triggers
Sometimes a trigger sends contacts into a path they are not ready for. Confirm that the correct segment or condition is being used to avoid misrouted contacts.
- Test with a sample contact
Run a test contact through the workflow to reproduce behavior and watch how the counters change after each step.
Best Practices for Reading GoHighLevel Workflow Stats
To get the most value from the statistics shown in each workflow:
- Check stats regularly, especially after publishing new automations.
- Track changes in execution and error counts after any configuration edits.
- Use tags or test contacts when experimenting with new logic paths.
- Monitor high-impact steps like triggers, filters, and messaging actions more closely.
When used consistently, these practices help you optimize your GoHighLevel workflows for performance and reliability.
Examples of Using GoHighLevel Stats in Real Scenarios
Example 1: High Executions, Low Results
If a promotion workflow shows many executions on email steps but few conversions, the stats confirm that messages are being sent while the problem likely lies in the offer or follow-up sequencing. In that case, you can adjust timing or add extra nurture steps in GoHighLevel to improve performance.
Example 2: Many Contacts Stuck in a Wait Step
When you see a large Contacts in step number on a Wait action, review the time settings or exit conditions. It may be that the delay is longer than intended or that conditions are too strict, keeping contacts in the wait state indefinitely.
Example 3: Spikes in Errors
If the Errors counter suddenly spikes on a webhook or external integration step, check connected systems and authentication. The stats in GoHighLevel act as an early warning system when something outside the platform changes.
Additional Resources for GoHighLevel Workflow Stats
To go deeper into how workflow statistics function behind the scenes, you can review the official documentation provided by the platform:
For broader strategy, funnel planning, and CRM implementation help that complements your GoHighLevel setup, you can also visit Consultevo for consulting and resources.
Using GoHighLevel Stats to Refine Your Automations
Workflow statistics are not just numbers; they are a practical feedback loop. By regularly checking how many contacts enter, wait, complete, or error at each step, you can refine your GoHighLevel automations to be more predictable, scalable, and effective.
Use the counters as an ongoing diagnostic tool: identify weak points, fix misconfigurations, test updates, and measure the effect directly in the workflow stats. Over time, this data-driven approach will help you build reliable automation systems that clearly show what is happening at every stage.
Need Help With ClickUp?
If you want expert help building, automating, or scaling your GHL , work with ConsultEvo — trusted GoHighLevel Partners.
“`
