GoHighLevel Workflow Maps: AI Assistant, Linked Workflows, Error Troubleshooting and Contact Journeys

Status check: everything here comes from HighLevel's official changelog entries dated 27 October 2026, linked in each section and in the sources below. Each entry says the same thing about access: Workflow Maps is available only to agency users and agency admins at launch. HighLevel's Founder Plan page also lists Workflow Maps among the features it describes as only available on the Founder plan. If you do not see it yet, check your user type and your plan before you promise it to a client.

Most of my debugging time in HighLevel is not spent fixing things. It is spent finding them. A client says a lead got the wrong text, and I end up opening six workflows, checking which tag starts which, and scrolling through execution logs one workflow at a time. Workflow Maps was already a big step, because it draws the whole sub-account for you from your existing workflows (see HighLevel's Workflow Maps introduction). These four additions are the parts that make it useful for real support work.

1. The AI assistant inside Workflow Maps

HighLevel's entry: Workflow Maps: Understand and manage automations with the AI assistant.

You open the Assistant from Workflow Maps and ask in plain language. It uses your workflow and map context, so the answers are about this account, not general advice. HighLevel lists what it can do:

• Understand a workflow: ask what a selected workflow does, or get a summary of a folder.
• Find and investigate: locate workflows by name, review issues, or ask about a workflow's connected assets.
• Focus the map: ask it to filter or highlight the workflows and folders you care about.
• Organise the account: create folders, move workflows, rename them or add notes.
• Build or edit workflows: describe the automation you want. Supported builds and edits run as background jobs.
• Review proposed actions: approval controls let you review plans and decide how supported changes are applied.

HighLevel's example prompts include "Explain what this workflow does", "Show only drafts in the Sales folder", "Create a welcome email and SMS workflow" and "Move these workflows into an Onboarding folder".

How I would use it

Taking over an account. When I inherit a sub-account built by someone else, the first job is working out what each workflow is for. Asking the assistant to summarise each folder gives me a first draft of my notes in minutes. I still open the important workflows to check, but I know where to look.

Tidying before handover. At the end of a build I like every sub-account to have clear folders and names. "Move these workflows into an Onboarding folder" and adding notes is exactly the boring work I am happy to hand over.

The limits to know

• The assistant works within your access permissions.
• Actions such as deletion and whole-map rearrangement still require confirmation, including when automatic approval is enabled.
• Saved views store filters only. They do not save the map's zoom, position or layout, so do not expect a saved view to bring back the exact picture you arranged.

2. Workflow Canvas: linked workflows side by side

HighLevel's entry: Workflow Maps: View linked workflows together in the Workflow Canvas.

Most real journeys are not one workflow. A form workflow adds a tag, the tag starts a nurture workflow, and that one adds the contact to a booking reminder workflow. Workflow Canvas, opened from Linked workflows in Workflow Maps, shows a workflow and the workflows linked to it together, including links across folders. You can:

• Explore the workflows linked to the one you selected.
• Follow handoffs created through shared assets or direct workflow actions.
• Use the map's asset-usage details to find the triggers or actions behind a shared asset.
• Open the builder when you need to change a step. Edits still happen in the builder, not on the canvas.

How I would use it

Client handover. HighLevel lists "explain a process that spans multiple workflows during a handover" as a use case, and this is where I will use it most. Instead of a long document, I can walk the client's team through lead capture, qualification and follow-up on one screen.

Before changing a tag. Renaming or removing a tag that three workflows depend on is how accounts quietly break. Checking which triggers and actions use that asset first saves a lot of pain.

One thing HighLevel is careful to say: connections show how the automation is configured. To see what actually happened to a person, use contact journeys.

3. Find and troubleshoot workflow errors

HighLevel's entry: Workflow Maps: Find and troubleshoot workflow errors.

Workflow Maps now shows workflow execution errors across the whole sub-account in one place. The flow is:

1. An errors badge marks workflows with errors from recent runs.
2. Select Review workflows with errors to see the flagged workflows, grouped into Published and Draft.
3. Use Has issues to narrow the map.
4. Select a workflow and review its failed executions, the affected step and the error details.
5. Open the workflow in the builder and fix the step.
6. Go back to the map and select Mark as read.

How I would use it: a failed webhook

Say a client's lead form sends data to an outside tool with a webhook action, and leads stop arriving there. Before, I would guess which workflow held the webhook and dig through its history. Now I open Workflow Maps, filter to Has issues, find the workflow with the badge, and read the failed execution and error details on the webhook step. Then I fix the URL or payload in the builder.

I would also make this a weekly check for any large sub-account I look after. A quick scan of Review workflows with errors catches broken integration steps before the client notices missed follow-ups.

Important: Mark as read is not a fix

HighLevel says it plainly: Mark as read clears the error badge. It does not repair the workflow or retry a failed execution. If you mark it read without fixing the step, the problem is still there, and any contacts that failed are not re-run for you. Fix it in the builder first, then mark it read so the badge means something next time.

4. A contact's journey across workflows

HighLevel's entry: Workflow Maps: View a contact's journey across workflows.

This is the one I have wanted for years. From the Contacts option in Workflow Maps you can:

• Search for a contact by name, email or phone number.
• Select them to focus the map on their workflow journey.
• Use the Workflows tab to see their enrollment history.
• Open Timeline to see runs, timestamps and execution statuses.
• Select a run to see its steps, then open the step you want to investigate.

The timeline shows runs that finished, are waiting or hit an error. Contact history covers the last 60 days.

How I would use it: "why did this contact get that SMS?"

This is the most common support question I get from agency clients. Now I search the contact by phone number, open Timeline, find the run around the time the message went out, and open the step that sent it. That tells me which workflow sent it and when. The same view answers "where is this lead stuck?", because a run that is waiting shows up as waiting.

Keep the 60-day window in mind. If a client asks about something from three months ago, this view will not cover it.

Who can use it, and what to tell clients

• Launch access: every one of these entries says Workflow Maps is available only to agency users and agency admins at launch. Your clients' sub-account users will not see it yet, so for now this is a tool for your team, not something to train clients on.
• Plan: HighLevel's Founder Plan page lists Workflow Maps among the features it says are only available on the Founder plan.
• One map per sub-account: HighLevel's introduction notes each sub-account has its own map.

My take: the assistant is handy, but the errors view and contact journeys are the real time savers. They turn "let me look into it" from an hour of clicking into a few minutes. If you look after many sub-accounts, start using them as part of your normal support routine.

For more of this week's HighLevel workflow news, see AI Builder filling in your workflow steps and my running LevelUp 2026 roundup.