Stop Rebuilding the Same GHL Account: A Workflow Audit Checklist

The workflow you inherited is lying to you

Every agency operator who works across multiple GoHighLevel accounts eventually runs into the same scene. You log into a client's sub-account. The workflows are all published. The pipeline looks active. On paper, everything is running.

Then you look closer. The "send SMS" action references a phone field that no longer exists. Three workflows point to a team member who left six months ago. A pipeline stage was renamed, and every automation branching on it now quietly skips the condition. Nothing has errored, because GHL does not error on quiet misfires. It just stops doing the thing it was meant to do.

Most accounts you inherit are in some version of this state. The automations "work" until you audit them and realise half of them have been broken for months. The client has no idea. They just see underperformance they blame on strategy.

Why this keeps happening

GHL makes it easy to build and hard to maintain. Custom fields get renamed. Users get deactivated. Pipelines get restructured. Each of those changes can quietly break an action inside a workflow, and GHL does not tell you about it.

The workflow builder has no linter. There is no "find all references to this field" button. There is no broken-link report. If you want to know whether your automations are actually doing what they are supposed to, you have to check every workflow, every action, every reference, by hand.

Which is why most people do not.

The audit checklist

Use this the next time you take over an account, onboard a new client, or just want to sanity-check your own setup. Work through each category. If you find issues in any of them, you have probably found the reason something is not performing the way the client thinks it is.

1. Deleted or inactive users

Any workflow that assigns tasks, sends internal notifications, or routes opportunities to a specific user will silently break if that user is removed from the account. The workflow still runs. The assignment just goes nowhere.

• Check every "Assign to user" action
• Check every internal notification action
• Check every task creation step with a specific assignee
• Check round-robin assignment pools for members who are no longer active

2. Missing or renamed custom fields

Custom fields get renamed or replaced all the time, especially during account restructures. Any action that references a field by its old name will fail quietly.

• Check all merge tags in email and SMS actions
• Check conditional logic that branches on custom field values
• Check any "update contact field" actions
• Check forms and surveys for orphaned field mappings

3. Broken pipeline stages

Pipeline stages get renamed, reordered, or removed as businesses evolve. Workflows that trigger on specific stage changes or route opportunities to specific stages misbehave when the stage they reference is gone.

• Check every "opportunity stage changed" trigger
• Check every "move opportunity to stage" action
• Check conditional branches that depend on current pipeline stage
• Check reporting workflows that summarise pipeline metrics

4. Orphaned tags

Tags are the connective tissue of most GHL automations, and they accumulate fast. Old campaigns leave tags behind. Experimental workflows leave tags behind. After a year of operation, most accounts have dozens of tags that no active workflow uses, and active workflows referencing tags that nobody applies anymore.

• Identify tags applied by workflows that no other workflow reads
• Identify tags referenced in triggers that are never actually applied
• Look for near-duplicate tags (lead-hot vs hot-lead) that split audiences unintentionally

This one is a good candidate for a regular tidy-up as part of your normal GHL automation routine, not just a one-off audit.

5. Stalled or infinite wait steps

A wait step that waits for a trigger event that can never fire is an automation dead end. Contacts sit in the workflow forever, blocking progression logic and polluting your analytics.

• Check wait-for-event steps for events that no longer exist
• Check wait-until-date logic for dates in the past that will never evaluate true
• Check wait-for-contact-action steps against the actions the contact is actually capable of taking

6. Duplicate or overlapping triggers

Multiple workflows firing on the same trigger is rarely intentional. It usually produces doubled-up messages, redundant tasks, or racing pipeline moves.

• Group workflows by trigger type and check for overlaps
• Check for two workflows reacting to the same form submission
• Check for two workflows reacting to the same tag being added
• Check for two workflows moving opportunities on the same stage change

7. Email and SMS delivery health

Even if the workflow logic is perfect, delivery can silently degrade. Bounced email domains, exhausted A2P 10DLC credits, and expired sender numbers all produce the same user-facing symptom. The messages just stop showing up.

• Check email send reputation on any custom sending domains
• Check A2P 10DLC registration status for SMS
• Check for workflows using deactivated or deleted phone numbers
• Review the last 30 days of email and SMS send logs for delivery rates

8. Form and webhook references

Forms get replaced. Webhooks get rotated. Any workflow triggered by a specific form ID or receiving data from a specific webhook endpoint will break when those upstream references change.

• Check form-triggered workflows against the forms actually in use on the site
• Check webhook triggers against the webhook endpoints actually receiving traffic
• Check outbound webhook actions for endpoints that now return 404

Doing this at scale

A thorough audit of a single sub-account, done manually, takes two to four hours. For a solo operator, that is a half-day. For an agency managing twenty sub-accounts, it is a month of work that nobody has budgeted.

This is exactly what the audit tool inside GHL Workflow MCP is built for. You ask it to audit an account, and it scans every workflow for the eight categories above. Deleted users, missing fields, broken stages, orphaned tags, the lot. It reports back with specific findings and suggested fixes, and the scan takes minutes instead of hours because it runs against the live account through your normal browser session.

For agencies that want a human review on top of the automated scan, or who inherited an account that needs a proper rebuild rather than a cleanup, the Audit Managed Service covers that end. Same checklist applied manually with context, with implementation included.

The hidden cost of skipping this

Most operators skip the audit because it does not feel urgent. The workflows appear to be running. The client has not complained. Why go looking for problems?

The cost shows up later. A broken lead-response workflow means missed conversions the client never attributed to you. A silently failing review-request sequence means fewer Google reviews than the client expected. A broken task-assignment workflow means leads dropped on the floor because nobody knew they existed.

Most of those losses are invisible. They do not produce error messages. They produce underperformance, which the client blames on strategy rather than plumbing. That is how broken automations become churn risks, and how a client you thought was happy turns into a client looking for a new agency.

Where to start

If you inherited an account recently, audit the deleted-users and renamed-fields categories first. Those two account for most of what tends to be broken. If you have been running an account for more than six months without a formal review, start with pipeline stages and tags, because those shift the most.

Pick one category from the checklist, run it against one account this week, and see what you find. In most accounts, the first thing you check is already broken. That is not a problem with the checklist. It is a sign of how normal silent breakage actually is.

If you want the short version of the tools that make this faster: Workflow MCP for self-serve scanning, Audit Managed Service for the done-for-you version, and the full product set if you want to see what else we have built for exactly this kind of work.