Anis Mahmud Anik

GoHighLevel Workflow Maps: Find Broken Workflows

Connected workflow nodes on a map, one marked with a green check and one with a red error badge, representing Workflow Maps.

Short answer

Workflow Maps shows every workflow in a sub-account, how they connect, and which assets they share, in one view. Announced on 27 October 2026, it lets you search for a workflow or an asset, trace one contact’s journey for the last 60 days, review workflows with errors, and spot unused workflows and empty folders. It is available to agency users and agency admins, and it is a Founder Plan feature. Marking an error as read only clears the badge; it does not fix the workflow.

In this post

  • What Workflow Maps is, and who can see it
  • How to open it
  • The four things it does
  • How to find a broken workflow in five steps
  • How to trace one contact’s journey
  • How to use Cleanup without breaking anything
  • What it cannot do
  • FAQ
  • Sources

What Workflow Maps is, and who can see it

Workflow Maps sits inside Automation, under Workflows. HighLevel’s Help Center describes it as a visual workspace that displays your existing workflows and their connections to supported assets, including tags, forms, calendars, pipelines, and custom fields. Each sub-account has its own map, and maps are generated from your existing workflows, so you do not need to create diagrams manually.

A form submission may start one workflow, which adds a tag that triggers another workflow. Before Workflow Maps, you had to open each workflow to see that chain. Now the map shows the chain: workflows in folders, assets beside them, and lines between them.

Availability, as published at launch:

  • Available only to agency users and agency admins. Sub-account users will not see it yet.
  • It is listed as a Founder Plan feature, so agencies on lower plans should check their own account before promising it to a client.
  • HighLevel’s Help Center also references Labs availability, and says to confirm whether Labs activation is required for your account. If you open Automation, then Workflows, and do not see Workflow Maps, check Labs first, then check your plan and your user role.

How to open it

  1. Open the relevant HighLevel sub-account.
  2. Go to Automation, then Workflows.
  3. Select Workflow Maps.
  4. You can also open Maps from inside a workflow’s builder.

Once the map is open, use Fit to display the complete view, then pan and zoom to inspect an area. Switch between 2D and 3D if your account offers both views. Use Search to find a workflow, asset, trigger, or action by name, and filters to narrow the view. If a workflow or asset is missing from the map, check the active filters first, then refresh the map data.

The four things it does

1. The map itself

The map shows workflows inside folders, with their connections to tags, forms, calendars, pipelines, and custom fields. Select any workflow or asset to see its details and its connections. Use Linked workflows to explore related workflows together in a focused view; HighLevel’s documentation also calls this interface Workflow view, while the release uses the term Workflow Canvas, so follow the labels shown in your account.

The practical use is before you change anything. Select the asset you are about to change, for example a tag, and check which workflows use it. The existing workflow posts on this site cover the same rule from the other side: a form trigger that filters on one form name will not fire for a second form with a similar name, and trigger filters that do not match the contact stop the workflow from starting. The map shows you those dependencies before the change, instead of after a client reports that follow-up stopped.

The map shows how automations are configured. It does not mean a particular contact has completed every visible connection. That is what Contact Journeys is for.

2. The AI assistant

Workflow Maps includes an AI assistant that answers questions about your automations, such as which workflows are connected to a particular asset, and helps with troubleshooting and account organisation. It can explain a workflow, apply filters to the map, reorganise folders, and request builds or edits, which run as background jobs under approval controls. HighLevel’s Help Center does not yet list everything the assistant can do, so test it in your account first.

Treat the assistant as a guide, not an editor, until you have tested it in your own account. Ask it to explain a workflow and point at the step that failed. Do not let it change a live workflow without you reading the change first. Actions such as deletion and whole-map rearrangement still require confirmation, including when automatic approval is enabled.

Workflow Maps now includes guided onboarding and a Resources hub. Open Help on the map to find guides for the task you want to complete.

3. Workflow errors, in one place

This is the part that saves the most time. Workflow Maps shows workflow execution errors across the whole sub-account in one place, instead of making you open each workflow’s log.

How to find a broken workflow in five steps:

  1. Open Automation, then Workflows, then Workflow Maps.
  2. Look for the errors badge. A badge marks workflows that encountered errors during recent runs.
  3. Click Review workflows with errors. The list separates Published workflows from Draft workflows.
  4. Use the Has issues filter to focus the map on flagged workflows only.
  5. Select a workflow to inspect its failed executions, the step that failed, and the error details. Use Open in builder to investigate and edit the affected step.

Then fix the step in the builder. The usual causes are the same ones in the workflows-not-triggering post on this site: the workflow is still a draft, the trigger does not match what is really happening, the trigger filters do not match the contact, or the contact cannot re-enter. Separately, check whether the contact is on Do Not Disturb or is missing the phone number or email address the step needs. The error details tell you which step failed; the log for that contact tells you why.

After you have reviewed an issue, click Mark as read to clear the badge. Mark as read clears the notification badge only. It does not repair the workflow, and it does not retry a failed execution. Clearing badges without fixing the step is the one mistake this tool makes easy, so fix first, then mark as read.

To inspect a past run from a workflow’s details, select Total Enrolled, choose an enrollment, and select the failed action to open its Event details.

4. Contact Journeys

Contact Journeys shows how one individual contact has progressed through multiple workflows. Search for a contact and review their enrollment history, including completed activities, waiting steps, and failed executions. The history window is the last 60 days.

Use Contact Journeys when a specific person says they never got a message. Use the main map when you want to understand how workflows connect. The two views answer different questions: the journey tells you what happened to one contact, the map tells you how the system is built.

How to use Cleanup without breaking anything

Workflow Maps includes Cleanup findings that flag possible maintenance work:

  • Workflows with default names.
  • Workflows without recent enrollments.
  • Empty folders.

Agency admins can organise supported workflows and folders, adjust their arrangement, and save shared map layouts. Saved organisational changes can affect other users who access the same sub-account, and access to view Workflow Maps does not necessarily include permission to modify or save its shared layout.

Cleanup identifies items for review. It does not automatically delete or fix anything, and the Help Center says not to assume it does. Treat every Cleanup finding as a question, not an order. A workflow with no recent enrollments may be seasonal, or it may be the backup for a campaign that runs once a quarter. Rename it or move it before you delete it, and check the map for anything connected to it first.

What it cannot do

  • It cannot edit workflow steps. To edit triggers, actions, or internal logic, open the workflow in Workflow Builder.
  • It cannot show a contact’s complete history. Contact tracing covers the last 60 days.
  • It cannot fix an error by clearing its badge. Mark as read only clears the notification.
  • It cannot automatically delete unused workflows. Cleanup only flags them.
  • It does not prove a contact completed a connection just because the connection is drawn on the map. The map shows configuration; the journey shows what actually happened.

FAQ

What is GoHighLevel Workflow Maps?
A visual workspace under Automation, then Workflows, that shows every workflow in a sub-account, how they connect, and which tags, forms, calendars, pipelines, and custom fields they share. It is generated automatically from your existing workflows.

Who can use Workflow Maps?
At launch, agency users and agency admins only. It is also listed as a Founder Plan feature. HighLevel’s Help Center says to confirm whether Labs activation is required for your account.

How do I find workflows with errors?
Open Automation, then Workflows, then Workflow Maps, and click Review workflows with errors. The list separates Published and Draft workflows. Select a workflow to see its failed executions, the step that failed, and the error details.

Does marking an error as read fix the workflow?
No. Mark as read clears the error badge. The underlying error still needs to be fixed in the Workflow Builder, and the failed execution is not retried.

How far back does a Contact Journey go?
60 days. Search for the contact in Workflow Maps and review their enrollment history, including completed, waiting, and failed activity.

Can I edit a workflow from the map?
No. Open the workflow in Workflow Builder to change its triggers, actions, or logic. The map is for seeing connections and finding problems, not for editing.

Does Cleanup delete unused workflows?
No. Cleanup flags workflows with default names, workflows without recent enrollments, and empty folders for review. Nothing is deleted automatically.

Need your workflows mapped and fixed?

If your account has workflows that stopped following up, or you inherited an account and nobody can explain what each automation does, book a free 30-minute call. The first step is a map of what you have, then a fix list.

Sources

Checked 2026-11-11. All GHL behaviour in this post comes from these sources, not from memory.

  • HighLevel Help Center, “Introduction to Workflow Maps in HighLevel Automation”. https://help.gohighlevel.com/support/solutions/articles/155000009497-how-to-use-workflow-maps-in-highlevel
  • HighLevel Help Center, “Review workflows with errors”. https://help.gohighlevel.com/support/solutions/articles/155000009464
  • HighLevel, “LevelUp Day 2026: The Next Evolution of HighLevel Features and Enhancements” (official LevelUp roundup, “Workflows: Introducing Workflow Maps” section). https://www.gohighlevel.com/post/levelup-day-2026-the-next-evolution-of-highlevel-features-and-enhancements
  • HighLevel Changelog, “Workflow Maps: Understand and manage automations with the AI assistant” (confirms the assistant capabilities, the approval controls, and that deletion and whole-map rearrangement still require confirmation, including when automatic approval is enabled). https://ideas.gohighlevel.com/changelog/workflow-maps-understand-and-manage-automations-with-the-ai-assistant
  • HighLevel Changelog, “Workflow Maps: Get started with guided onboarding and Resources” (confirms the guided onboarding and Resources hub). https://ideas.gohighlevel.com/changelog/workflow-maps-get-started-with-guided-onboarding-and-resources

Related reading