Flow Inspector: First Time Setup Guide

If you’ve ever stared at a GoHighLevel contact wondering why an automation did something it shouldn’t have (or didn’t do something it should have), Flow Inspector is built for that moment.

It pulls together everything that happened to a contact across every workflow they touched, lays it out as a visual timeline, and shows you the exact timing between each step. Instead of cross-referencing execution logs and audit trails manually, you get a single view that makes the sequence of events obvious.

By the end of this guide you’ll have Flow Inspector connected to your GHL account, the Chrome extension installed, and your first complete contact timeline loaded with step-level detail inside every workflow column.

Plan for about 15-20 minutes the first time through. Most of that is the GHL setup steps. Once you’ve done it once, loading a new contact only takes a few minutes.

To get started, you’ll need to have the following prerequisites:

You’ll need two pieces of information from GHL before you can connect Flow Inspector: an API token from a Private Integration and your Location ID. Get both before moving to Step 2.

In the GHL sub-account that you want to connect to Flow Inspector, navigate to Settings → Private Integrations and click Create New Integration.

Give it a name you’ll recognize (“Flow Inspector” works well), and optionally a description and click Next.

Under Scopes, enable the following scopes and nothing else:

Note all scopes are Read Only scopes; Flow Inspector never writes to, or deletes data from your GHL account.

Click Create on the integration. GHL will display your API token once, so copy it immediately and save it somewhere safe temporarily before navigating away. It will not be shown again. If you lose it you’ll need to Rotate and Expire it and reconnect Flow Inspector.

Your Location ID is visible in the URL address bar while you’re anywhere inside your GHL sub-account. You don’t need to navigate away from the Private Integration screen, look at the URL right now and you’ll see it.

It’s the alphanumeric string that appears after /location/ in the URL:

https://app.gohighlevel.com/location/OgqIuof6vYHWK0jXuKqp/settings/private-integrations/

In the example above, OgqIuof6vYHWK0jXuKqp is the Location ID. Copy that value and keep it alongside your API token. You’ll need both in the next step.

With your API token and Location ID in hand, head to go.flowinspector.app and log in to your account.

In the left sidebar, click Services Setup.

You’ll see the Connect to GHL API card. Paste your API token in the Access Token field, and enter your Location ID in the Location ID field and click Connect and save account.

Flow Inspector will validate your credentials and confirm all four required scopes are active. If everything checks out, your workflow list will load automatically: you’ll see it populate in the Workflow map to the right. This is your full list of automations from the connected GHL sub-account and is used later when adding missing workflows to a timeline.

If your agency uses a white-label GHL domain, you’ll need to configure this before loading any timelines or contact CSV files. All links that Flow Inspector generates, including your contact’s audit log page, workflow execution log pages, and contact record, open inside your GHL account. If those links use the wrong domain, they’ll break.

Expand the Custom GHL Domain section by clicking Step 3 in the Connect to GHL API card. Enter your custom domain in the format app.mycustomdomain.com (or whatever your custom domain/subdomain is) – no https://, just the domain itself – and click Save.

If your agency runs on the default GHL domain you can skip this entirely. Flow Inspector uses app.gohighlevel.com by default.

Not sure if you have a custom domain? Try opening your GHL account in a fresh browser tab and look at the URL. If it shows anything other than app.gohighlevel.com you have a custom domain and should configure it here.

Flow Inspector’s Chrome extension is what takes your timeline from a high-level map to a full diagnostic view. Without it you can see which workflows fired and when, but you can’t see what happened inside them. The extension adds step-level detail to every workflow column, which is where the real diagnostic value lives.

Open Google Chrome and head to the Chrome Web Store. Search for GHL Flow Capture or use this direct link:

Click Add to Chrome and confirm the installation. The extension installs in seconds and requires no configuration. Once it’s active it works automatically in the background whenever you’re inside GHL.

You’ll see the Flow Inspector icon appear in your Chrome toolbar when the extension is active. It’s recommended to pin it to your toolbar so it can be easily used while grabbing the JSON content of the Execution Log for each automation.

With Flow Inspector connected and the Chrome extension installed, you’re ready to load your first timeline.

In the left sidebar, click Services Setup. You’ll see the Find Contact card in the right column at the top of the screen.

You have two options:

• Search by name or email: Type in the search field and click Search. Flow Inspector will query your connected GHL sub-account for matching contacts.
• Load recent contacts: Click Recent to pull the 10 most recently created contacts from your account, then select the one you want.

If you’re running this for the first time, pick a contact who has a known automation history, ideally someone who has gone through at least a couple of workflows recently. A contact with a complex or problematic automation history will give you the most to work with.

Once you’ve selected your contact, you’ll need to export their audit log from GHL and import it into Flow Inspector. Here’s the full process:

1. In the Find Contact card, click Open Audit Log → Export CSV. This opens your contact’s audit log page in GHL in a new browser tab.
2. In the GHL tab, click Export and then click Export again on the confirmation popup.
3. Click Check Progress on the popup, then click Download File next to the audit log you just exported.
4. Save the CSV file to your computer.
5. Back in Flow Inspector, drag the CSV file onto the Import CSV card in the right column, or click the card to browse and select the file manually.
6. Once the file is loaded, Flow Inspector switches automatically to the Timeline tab and builds your initial timeline view.

What you’ll see at this point is the skeleton, the major automation touch-points GHL captured, laid out in chronological order with elapsed time between each event. This is a starting point, not the complete picture. GHL’s audit log rarely captures every workflow that fired for a contact, and it contains no step-level detail inside each workflow.

The next two steps complete the picture.

GHL’s audit log CSV is a useful starting point but it doesn’t tell the whole story. It frequently omits workflows that fired for a contact, sometimes minor ones, sometimes critical ones. If you’re diagnosing an automation problem, a missing workflow in your timeline could mean missing the root cause entirely.

Flow Inspector accounts for this gap. To add missing workflows, look for the Import missing workflows panel that appears automatically after your CSV loads. Click the search bar inside the panel and select the workflows you want to add from the list. You can select multiple at once. Once you’ve made your selections, click Add columns to add them all to your timeline in one step.

Your workflows are now ready for the real heavy-lifting in the next step.

This is where your timeline goes from a map to a full diagnostic view. Each workflow column in your timeline currently shows you that a workflow fired and when, but not what happened inside it. Importing the execution log JSON from the Chrome extension adds step-level detail to every column, showing you exactly what each action did and the precise timing between steps.

You’ll repeat this process for each workflow column in your timeline.

For each workflow column:

1. In Flow Inspector, click the workflow column header (the automation title). This opens the GHL execution log for that workflow in a new browser tab.
2. Once the execution log fully loads, the GHL Flow Capture extension icon turns green, meaning it’s ready to capture.
3. Click the Flow Inspector extension icon and then click Copy JSON in the extension panel.
4. Back in Flow Inspector, click the Import Steps button on the workflow column and paste the JSON you just copied.
5. The column updates with full step-level detail: every action, every condition evaluation, every wait step, with precise timestamps and elapsed time between each one.

Repeat steps 1-5 for every workflow column in your timeline.

If the GHL Flow Capture extension displays a warning that logs are paginated or incomplete, it means the execution log is showing fewer actions than actually fired. GHL defaults to displaying 10 actions per page and the extension can only capture what’s visible.

To fix it, scroll to the bottom of the GHL execution log page and change the display count from 10 to 50, then refresh the page. Once the full execution log is visible, click the extension icon again and copy the JSON. The incomplete warning should be gone and the full step-level detail will be captured.

Your timeline is now complete. Every workflow that fired for this contact is accounted for, and every column has full step-level detail. You’re looking at something GHL’s own UI can’t show you: the complete sequence of everything that happened to this contact, in order, with precise timing between every step.

For future reference, here’s the full process in four concise steps:

1. Connect – enter your Location ID and API token in the Services Setup tab
2. Load – find your contact, export their audit log CSV from GHL, and import it into Flow Inspector
3. Complete – add any workflows the CSV missed using the Import missing workflows panel
4. Detail – import the Chrome extension JSON for each workflow column to add step-level detail

Once you’ve done this a few times it becomes second nature. The GHL credential setup in Step 1 is one-time only, every timeline after this starts at Step 4.