How to Check GoHighLevel Workflow Version History (Before Black Friday Goes Live)

Let ChatGPT check your live GoHighLevel workflow for you. Try TinyFish free. New accounts start with $8 in Wallet funds.

TL;DR

Before a big campaign goes out, you want to know one thing: is the live workflow the one you meant? GoHighLevel workflow version history answers that, but it takes clicks, and one wrong click can restore or publish something. This guide shows how to ask ChatGPT or Claude, with the TinyFish app connected, to open your workflow read-only and list every saved version, its status, its timestamp and which one is live. It changes nothing.

A quick disclosure: I work at TinyFish, which gives ChatGPT and Claude live web access, including a browser agent that can click through real websites for you.

Why check before Black Friday

Black Friday is Friday, November 27, 2026. If your offer emails, SMS follow-ups and tags all run through one GoHighLevel workflow, that workflow is the most important thing in your account this month.

Small teams edit workflows in a hurry. Someone tweaks a wait step, someone else changes a discount code, and nobody is quite sure which version is published. A five-minute check the week before saves you from finding out on the day.

What GoHighLevel workflow version history keeps

A few facts from HighLevel's own help page, so you know what the check can and can't show (HighLevel: Workflows Version History & Restore):

• Each entry shows a version number (v12, v13 and so on), a timestamp, the editor who saved it, and a status: Draft or Published.
• It keeps up to 10 versions or 30 days, whichever comes first. Anything older is gone.
• Versions are created when you click Save, use Save Version, confirm the Unsaved Changes pop-up, or change the status between Draft and Published. Routine auto-saves don't create a version on their own.
• Restoring a version reopens it as a new draft. Your live workflow doesn't change until you publish.

At launch, HighLevel made Version History available through Labs, so if you can't see it, check Settings > Labs in your account.

What you need

• ChatGPT or Claude with the TinyFish app. Install it once by following the plugin docs. After that you ask in plain English, and TinyAgent opens the site in a real cloud browser and reports back.
• A saved GoHighLevel login in TinyProfiles. You sign in to GoHighLevel once in a secure TinyFish browser profile. Later tasks reuse that signed-in session, so the agent skips the login. TinyFish never needs your password in the chat. If the profile isn't signed in, the agent stops and asks you to sign in.

The prompt

This is the exact prompt our engineering team tested. Paste it as is:

Use TinyFish with my saved GoHighLevel login to open the marketing workflow, read-only. Confirm its status and current version, open Version History, and list each retained version with its status and timestamp and which one is live. Don't save, publish, restore, revert, test or edit anything. If an unsaved-changes prompt appears, stop without saving or discarding.

If you have more than one workflow, name the one you mean exactly as it appears in GoHighLevel. Here's the same prompt for an invented candle shop:

Use TinyFish with my saved GoHighLevel login to open the workflow named "BF 2026 Early Access", read-only. Confirm its status and current version, open Version History, and list each retained version with its status, timestamp and editor, and which one is live. Don't save, publish, restore, revert, test or edit anything. If an unsaved-changes prompt appears, stop without saving or discarding.

Why the prompt says what not to do

This runs on your real account, on a workflow that may be sending messages to customers right now. So the prompt spells out every action that could change something: save, publish, restore, revert, test, edit.

The unsaved-changes line matters too. In GoHighLevel, confirming that pop-up creates a new version. Discarding it throws away someone's work. Neither is the agent's call to make, so it stops and tells you.

The result is a check you can run any time, even mid-campaign, without worrying that it touched anything.

What you get back

A short summary of the workflow, then a list of versions. Expect:

• Workflow status: Published or Draft.
• Current version: the version number the builder shows.
• Version list: each retained version with its number, status and timestamp, and the editor if you asked for it.
• Which one is live: the published version, called out clearly.

Example output (invented business)

Here's how to read that. The live version is v14. There's a newer draft, v15, that hasn't been published. If v15 holds the discount code you meant to send, you now know to publish it yourself before Black Friday.

Tips

• Let it run. Opening a workflow and its history takes a few minutes. Don't stop it halfway.
• Name the workflow exactly. "The marketing workflow" works if you only have one. If you have several, copy the name from GoHighLevel.
• You make the changes. The agent only reads. If you need to restore or publish a version, do it yourself in GoHighLevel, where you can see the preview first.
• Check a week ahead and again the day before. Version History only keeps 10 versions or 30 days, so an early snapshot is worth saving in your notes.

When it doesn't work

• "Can't find a signed-in session." Your TinyProfile isn't signed in to GoHighLevel, or the session expired. Sign in again in the profile and rerun the prompt.
• It opened the wrong workflow. Give the exact name, or paste the workflow's link from your browser.
• No Version History panel. Your account may not have the feature turned on. Check Settings > Labs, or ask your agency admin.
• ChatGPT asks about a step limit first. That's normal. Confirm and let it start.

Want to see this live? We're running it at TinyFish Small Business Week, a free 45-minute live session on Thu Nov 19, 11 AM ET. Save your seat, and bring the job you want off your plate.

Check your live workflow before the big send. Start free on TinyFish.