v1.4.1 - reach the example

The example report was only linked from the report page, which cannot be opened before your first audit. It is now a link in the popup footer, next to rules.

v1.4.0 - example account

Adds a built-in example account: panel.html?demo=1, or the see an example report link on the report page before you have run anything.

It is a fictional company run through the real detectors — the findings are genuinely produced by the same code that runs on a live account, not written by hand. That makes it safe to screenshot for the Web Store listing without publishing any client's workflows, and it gives the extension a real empty state.

Two zips as before: the plain one installs unpacked, the -webstore one has the manifest at the root.

v1.3.0 - icons and Web Store prep

Adds a real icon (no more grey puzzle piece), a privacy policy, and everything needed for a Chrome Web Store listing.

Two zips here:

• ghl-workflow-auditor-v1.3.0.zip - what you install unpacked. Includes INSTALL.txt.
• ghl-workflow-auditor-v1.3.0-webstore.zip - manifest at the root, for uploading to the Web Store.

No behaviour changes.

v1.2.0 - a hundred findings you can actually read

Quality of life. No detector changes — v1.1.0 found 102 things on a real account and the report was a scroll.

Filters. Severity chips, published-only, free text search, and a group by workflow toggle so everything wrong with one workflow is in one place. Sticky header, so you keep the columns past row 20.

Everything links into GoHighLevel. Findings and inventory rows open that workflow. The link was already in the JSON and no view used it.

Copy buttons. Next to every download, and one per finding. Pasting a line into a ticket, or the whole dump into an AI agent, no longer goes through your Downloads folder.

Filenames you recognise. audit-Acme-Co-2026-09-11.md instead of audit-lwX75iqdycbLfO2P9bdh-2026-09-11.md.

Popup breakdown. HIGH / MEDIUM / LOW separately, plus how many are in published workflows. Opening the report focuses the tab you already have open instead of stacking a third one.

Better empty states. A clean account is told so. A second run with no drift says nothing changed instead of showing you an empty diff.

---

Updating: replace the files in your install folder and reload in chrome://extensions. Your rules survive.

v1.1.0 - the workflow is a graph

A workflow is a graph, not a list

next is a string on a linear step and an array on anything that branches; a goto jumps through attributes instead of next entirely. Walking it as a chain stopped at the first If/Else. Against a real 66-workflow account that left 449 of 613 steps out of the traversal — while the JSON dump claimed they were in execution order.

Every branch is now followed and labelled with the name shown on the canvas. Steps carry the path they sit on (main > Lead). Loops and orphaned steps come back as findings.

It can see pipelines now

Opportunity, pipeline and ownership values live in __customInputFields__ as {filterField, value} pairs, not as plain properties. That was 125 steps and 14 stages invisible on the reference account — including 22 assign steps that own nobody at all.

New detectors

Loops · unreachable steps · missing else arms · wait-for-reply beside an AI agent · condition waits nothing resets · year-long parks · assignment to an empty list · merge fields with no upstream gate · opportunities with no lookup or no stage · stages crossed in zero seconds · duplicate triggers across published workflows · webhooks still pointing at ngrok.

On the reference account: 47 findings → 102.

Ranked by what is actually happening

Severity is the rule, impact is whether anyone is exposed. Published before draft, then by how many contacts are inside right now.

What changed since last time

Every run stores a snapshot. The next one opens with what was edited, published, renamed, added or deleted — so you re-audit the three workflows someone touched, not all sixty.

---

Updating: replace the files in your install folder and hit reload in chrome://extensions. Your rules survive.

v1.0.0

First public release.

Unzip, then chrome://extensions → Developer mode → Load unpacked → pick the folder. Full instructions in INSTALL.txt inside the zip.

Open a GoHighLevel sub-account and click the icon. Nothing to configure, nothing to paste.