Workflow Version History in HighLevel
Workflow Version History in HighLevel keeps up to 10 saved versions or 30 days of history per workflow. Each entry records the editor’s name, timestamp, and draft or published status. Click Restore to reopen any version as a new draft – your live workflow is untouched until you Publish. Use Create new workflow from version to branch a past state into a separate workflow. Undo/Redo handles same-session edits. All three tools are included at no extra cost.
Workflows get edited. Sometimes an edit breaks something.
Version History exists so that a bad change never becomes a permanent problem.
Reading time: approximately 8 minutes.
Edit HighLevel workflows with confidence knowing – start your free trial today
Version History, Auto-Save, and Undo/Redo are all included on every HighLevel plan. Start your free trial today.
What Is Workflow Version History in HighLevel?
Workflow Version History is a built-in safety net inside the HighLevel Workflow Builder.
Every time you save a workflow, HighLevel records the complete state of that workflow as a version entry. Each entry captures who made the edit, exactly when it happened, and whether the workflow was in draft or published status at that moment.
You can browse up to 10 saved versions or 30 days of history – whichever limit arrives first. Any version can be restored as a new draft at any time.
Your live published workflow keeps running unchanged until you explicitly publish the restored draft.
The feature was revamped in 2025 with a redesigned sidebar, filterable by editor, and cleaner version labels such as v12, v13, v14 to make navigation fast even on heavily edited workflows.
The Editing Trifecta: Three Tools That Work Together
HighLevel describes Version History, Auto-Save, and Undo/Redo as the “Editing Trifecta.” Each one handles a different type of editing scenario. Understanding which tool to reach for saves time and prevents accidental data loss.
Saves canvas changes automatically as you work. No manual save required.
A “Saving…” and “Auto Saved” indicator confirms progress is captured. Manual Save is still available if you prefer it.
Session-based controls for reversing or reapplying the most recent canvas edits. History resets when you close the tab or refresh.
Use for mistakes made moments ago in the current session.
Persistent, shared checkpoints across sessions. Any team member can browse, filter, and restore past versions.
Use for recovering changes from a previous session or made by another editor.
The rule of thumb: use Undo/Redo for the last few minutes of your current session. Use Version History for anything older than that, or for anything another team member changed.
How Version History Works
What Gets Recorded
A new version is automatically recorded when you save the workflow manually, when you publish the workflow, and when significant structural changes are detected on the canvas.
You can also manually name and save a version at any point. Named versions appear in the sidebar with your label rather than just a timestamp, making them much easier to find in a long version list.
What Each Version Entry Shows
Every entry in the Version History sidebar shows the version number label such as v14, the name of the editor who saved it, the date and time of the save, and whether it was a draft or published build at that moment.
The sidebar can be filtered by editor. On workflows touched by multiple team members, this filter is essential for finding the right version quickly.
How Restore Works
Clicking Restore beside any version reopens it as a new draft. Your currently published workflow keeps running unchanged.
The restored state becomes a new version in the history list.
All prior versions remain available after a restore – nothing is deleted. Two conditions must be met before restoring: the workflow must be in Draft mode, and no contacts can currently be enrolled in the workflow.
Create New Workflow From Version
Instead of Restore, you can select Create new workflow from version. This branches the selected past state into a completely separate new workflow without touching the original in any way.
Use this when you want to test a major rebuild or explore a structural change without any risk to the current live automation.
Draft vs. Published: An Important Distinction
Saving and publishing are two independent actions in the Workflow Builder.
A workflow can be saved with unsaved changes still on the canvas, or saved and still sitting in Draft. You must explicitly click Publish for any changes – including restored versions – to go live.
This separation is what makes Version History safe to use: restoring always creates a draft, never a live workflow.
What You Can Do With It
- Recover from a bad edit by restoring the last known good version as a draft, reviewing it on the canvas, and republishing without the mistake ever reaching your live contacts
- Audit who changed what and when by browsing the version sidebar filtered by editor – each entry names the person who saved it and the exact timestamp, giving you a clear accountability trail on shared workflows
- Roll back a client’s workflow after they made changes that broke the automation, by finding the last working version and restoring it without affecting the live workflow until the restore is reviewed and published
- Branch a workflow for safe experimentation by using Create new workflow from version to build a structural variant without any connection to the original, then test it independently before deciding whether to adopt the changes
- Name milestone versions before major rebuilds so you always have a labeled restore point such as “Stable v3 before A/B test” that is easy to find in the sidebar even after many subsequent edits
- Coordinate team editing by using Save Version before handing a workflow off to another editor, so both editors have a clear checkpoint to reference if the next round of changes needs to be undone
- Undo a session mistake instantly using Ctrl Z or Cmd Z without opening Version History at all – Undo/Redo handles the last few minutes of a current session without any version management overhead
Key Definitions
| Term | What It Means |
|---|---|
| Version History | A persistent, shared record of every saved state of a workflow. Stores up to 10 versions or 30 days of history per workflow. Accessible from the Version History icon in the Workflow Builder sidebar. Revamped in 2025 with a cleaner sidebar, editor filter, and clearer version labels. |
| Version Entry | A single record in the Version History sidebar representing one saved state of the workflow. Each entry shows the version number label (v12, v13…), the editor’s name, the timestamp, and the draft or published status at the time of the save. |
| Restore | The action of reopening a past version as a new draft in the Workflow Builder. Does not affect the currently published workflow. Requires the workflow to be in Draft mode with no contacts currently enrolled. All prior versions remain available after a restore – nothing is deleted. |
| Create New Workflow From Version | An alternative to Restore that branches a past version into a completely separate new workflow. The original workflow and its published state remain entirely unchanged. Used for safe experimentation with major structural changes. |
| Named Version | A version that has been manually saved and labeled with a descriptive name at a milestone point – for example, “Pre-enterprise branch rebuild.” Named versions appear in the sidebar with the label instead of just a timestamp, making them easier to locate in long version lists. |
| Draft/Publish Toggle | The control in the top-right corner of the Workflow Builder that determines whether the workflow is actively running. Draft mode means the workflow will not fire for real. Published mode means it fires when trigger conditions are met. Saving and publishing are independent – a saved workflow must be explicitly published to go live. |
| Undo / Redo | Session-based controls that reverse or reapply the most recent canvas edits in the current editing session. Keyboard shortcuts: Ctrl/Cmd+Z for Undo, Ctrl+Y or Cmd+Shift+Z for Redo. History resets when the session ends – on tab close, page refresh, or version restore. Not shared between team members. |
| Recent Changes | A session-based timeline inside the Workflow Builder that shows a chronological list of all edits made in the current session. Clicking any entry jumps the canvas to that point in time. Resets when the session ends. Different from Version History, which records persistent saved states across sessions. |
| Auto-Save | A feature that automatically saves canvas changes as you work. Displays a “Saving…” and “Auto Saved” indicator to confirm progress is captured. Manual Save remains available for users who prefer full manual control. Part of the Editing Trifecta alongside Undo/Redo and Version History. |
| Editing Trifecta | HighLevel’s term for the three complementary workflow editing safety features: Auto-Save, Undo/Redo, and Version History. They work together at no extra cost. Auto-Save handles continuous capture. Undo/Redo handles same-session reversals. Version History handles persistent cross-session recovery. |
Use Cases by Scenario
Version History is a utility feature rather than a marketing channel, so this section covers real scenarios where it saves time, prevents damage, and protects live automations.
Agency Rebuilds a Client Workflow
An agency is hired to improve a client’s lead nurture workflow that has been running successfully for six months. Before making any changes, the agency saves and names the current version: “Stable pre-rebuild March 2026.”
Two hours into the rebuild, the agency realizes the new branching structure is more complex than expected and may need to be rethought. They restore the named stable version as a draft, review it, and republish – the client’s live workflow never missed a beat and all contacts that entered during the rebuild were handled by the original published version.
Outcome: Major workflow changes are made without any risk to the client’s live automation, and a clean restore point is available if the new build does not work as intended.
Team Member Makes an Accidental Deletion
A team member is editing a complex 40-step workflow and accidentally deletes a branch containing six actions. They close the tab before noticing.
When they reopen the workflow, the deleted branch is gone and Undo history has reset with the session.
They open Version History, find the version saved 20 minutes before the deletion, and restore it as a draft. The deleted branch is back.
They publish the restored draft and continue editing from there.
Outcome: A significant accidental deletion is recovered in under two minutes without any rebuild work, because the version was auto-saved before the error occurred.
Client Makes Unauthorized Changes
A sub-account client has edit access to their own workflows. They make several changes to their appointment reminder sequence trying to “optimize” it.
Response rates drop. The agency reviews the execution log and identifies the changes as the cause.
The agency opens Version History, filters by editor to find the last version saved before the client’s edits, and restores it as a draft. They review the restored version, confirm it matches the original working build, and republish it.
Outcome: The working workflow is restored without the agency needing to rebuild it from memory or screenshots, and the fix is live within minutes of identifying the problem.
Testing a Major Structural Change
A business wants to add an enterprise client branch to a workflow that currently handles standard leads. The branch will add 15 new steps and significantly change the routing logic.
Rather than editing the live workflow directly, they open Version History and select Create new workflow from version on the current published state.
The new workflow is built and tested in isolation over several days. Once confirmed working, the original workflow is updated with the enterprise branch logic.
The test workflow is archived. The original workflow’s version history is unaffected throughout the entire process.
Outcome: A complex structural change is developed and tested without any risk to the live workflow serving current leads during the development period.
Multi-Editor Team Coordination
Three team members share editing access to a set of onboarding workflows. Before each editing session, the editor saves and names a version – “Pre-edit: [Name] [Date]” – so the team has clear checkpoints matching each person’s work.
When a conflict arises about which version of the welcome email step is the correct one, the team filters Version History by editor and compares the two versions side by side using Preview. The correct version is identified and restored in minutes without any team meeting or manual review of notes.
Outcome: Multi-editor workflows are managed without version confusion because every editor creates a named checkpoint before starting their session.
Build and edit HighLevel workflows with a full – start your free trial today
Version History, Auto-Save, and Undo/Redo are included on every HighLevel plan at no extra cost. Start your free trial today.
Who Is This For?
Especially Useful If You…
- Run an agency managing workflows for multiple clients and need to make edits without risking damage to live automations that are actively serving contacts
- Work on workflows in a team where multiple editors may touch the same workflow, and you need a clear accountability record of who changed what and when
- Give clients sub-account access to their own workflows and need a fallback option for when a client makes changes that break the automation
- Regularly test major structural changes to high-volume workflows and want a safe way to develop those changes without affecting the live version during development
- Build complex multi-step workflows where accidental deletions or incorrect edits would require significant time to manually rebuild
Less Critical If You…
- Build simple 3 to 5 step workflows with a single editor that are easy to rebuild from memory if something goes wrong – Version History still helps, but the stakes are lower
- Rarely edit published workflows once they are live, because Version History is most valuable in active editing and iteration scenarios rather than set-and-forget automations
- Need version history beyond 30 days or more than 10 versions – the current limits are what they are, and if you need a longer audit trail you will need to supplement with manual naming practices
How to Use Workflow Version History
Step 1: Open the Workflow and Access Version History
Go to Automation, then Workflows. Open the workflow you want to review.
In the Workflow Builder, click the Version History icon in the sidebar. The Version History panel opens on the right side of the canvas.
Step 2: Browse and Filter the Version List
Scroll through the chronological version list. Each entry shows a version label such as v14, the editor’s name, the timestamp, and draft or published status.
Use the editor filter to narrow the list if you are looking for changes made by a specific team member.
Step 3: Preview Before Restoring
Use the Preview or Compare function to review a version before committing. Confirm that the version you are about to restore is the correct state.
If it is not, continue browsing other versions.
Step 4: Confirm Restore Conditions
Before clicking Restore, confirm two things. First, toggle the workflow to Draft mode using the Draft/Publish toggle in the top-right corner.
Second, confirm no contacts are currently enrolled in the workflow – check the enrollment count and wait or remove contacts if needed.
Step 5: Restore the Version as a Draft
Click Restore beside the version you want. The selected version reopens as a new draft.
Your published workflow keeps running the previous published version without interruption. All prior version entries remain in the sidebar – nothing is deleted by the restore.
Step 6: Review and Publish
Review the restored draft carefully on the canvas. Make any additional adjustments needed.
When ready, click Publish to push the restored version live. Until you publish, the live automation is untouched.
Step 7: Branch Into a New Workflow for Big Changes
For major structural rebuilds, select Create new workflow from version instead of Restore. This creates a completely separate new workflow from the past state.
Build and test the new workflow in isolation. The original remains live and unchanged throughout.
Step 8: Use Undo/Redo for Same-Session Mistakes
For any mistake made moments ago in your current session, press Ctrl Z or Cmd Z to undo. Press Ctrl Y or Cmd Shift Z on macOS to redo.
Click Recent Changes on the canvas to jump to any earlier point in the current session. Remember the history resets on tab close or refresh.
Step 9: Name Versions at Milestones
Before any major editing session, manually save and name a version: for example, “Stable before Q2 rebuild” or “Pre-enterprise branch.” Named versions appear in the sidebar with the label instead of just a timestamp. On a workflow with 10 or more versions, named checkpoints are the difference between a 10-second restore and a 10-minute search.
How It Connects to the Rest of HighLevel
- Workflow Builder – Version History is a native feature of the Workflow Builder. It is accessed from inside the builder canvas and records versions of the workflow canvas state including all actions, triggers, branches, and settings configured at each save point.
- Advanced Workflow Builder – complex multi-branch workflows with many conditional paths are the scenarios where Version History provides the most value. The more complex the workflow, the harder it is to manually rebuild a state, and the more important a versioned restore point becomes.
- Tag-Based Automation – tag-triggered workflows that are actively enrolling contacts are the most common scenario where the restore conditions matter. If a tag trigger is firing frequently, there may always be enrolled contacts making a restore window difficult to find without pausing the trigger temporarily.
- Multi-Channel Campaigns – multi-channel workflow sequences with many actions across SMS, email, voicemail, and social channels are high-value automations where a version history restore prevents hours of rebuild work if an edit goes wrong.
- Appointment Reminders – appointment reminder workflows run continuously and are frequently edited to adjust timing, add channels, or update message content. Version History provides the restore safety net that makes iterating on these live workflows practical.
Common Questions
Quick Answer: Workflow Version History keeps up to 10 versions or 30 days of history per workflow. Each entry shows the editor name, timestamp, and draft or published status. Click Restore to reopen any version as a new draft – your live workflow is unchanged until you Publish. Use Create new workflow from version to branch into a separate workflow. Restore requires: workflow in Draft mode, no enrolled contacts. Use Undo/Redo for same-session mistakes. Name versions at milestones for faster recovery. All three Editing Trifecta tools are included at no extra cost.
What is Workflow Version History in HighLevel?
A built-in record of every saved state of a workflow. Stores up to 10 versions or 30 days of history.
Each entry captures the editor’s name, timestamp, and draft or published status. Restored versions become new drafts – your live automation is unchanged until you Publish.
How many versions does HighLevel Workflow Version History keep?
Up to 10 saved versions or 30 days of history per workflow, whichever limit is reached first. Each version is labeled chronologically (v12, v13…) and filterable by editor.
Versions beyond the 10-version or 30-day window are no longer accessible.
How do you restore a workflow version in HighLevel?
Open the workflow builder, click the Version History icon in the sidebar, find the version you want, and click Restore. The workflow must be in Draft mode with no enrolled contacts.
The restored version opens as a new draft. Your published workflow keeps running until you review and publish the draft.
Does restoring a workflow version affect contacts currently in the workflow?
No – restoring creates a new draft and does not affect the published workflow or enrolled contacts. The live automation keeps running the published version.
However, restoring requires no contacts to be enrolled, so you may need to wait or remove them first.
What is the difference between Version History and Undo/Redo in HighLevel?
Version History is persistent and shared – any team member can browse and restore past states across sessions. Undo/Redo is session-based – it reverses your most recent edits in the current session only and resets when you close the tab or refresh.
Use Undo/Redo for recent mistakes. Use Version History for anything older or made by another editor.
What is the Recent Changes list in HighLevel?
A session-based timeline in the Workflow Builder showing all edits made in the current session. Clicking any entry jumps the canvas to that point.
It resets when the session ends. Different from Version History, which records persistent saved states across sessions.
Can you create a new workflow from a previous version in HighLevel?
Yes. In the Version History sidebar, select Create new workflow from version instead of Restore.
This branches the past version into a completely separate new workflow without touching the original. The original workflow and its published state remain entirely unchanged.
What is the Editing Trifecta in HighLevel workflows?
HighLevel’s term for Auto-Save, Undo/Redo, and Version History working together. Auto-Save handles continuous capture.
Undo/Redo handles same-session reversals. Version History handles persistent cross-session recovery.
All three are included at no extra cost.
What is the Draft/Publish toggle in HighLevel workflows?
The control that determines whether the workflow fires for real. Draft mode means no live triggering.
Published mode means it fires when conditions are met. Saving and publishing are independent – you must explicitly click Publish for any change to go live.
A restored draft requires a manual Publish before it affects live contacts.
When does HighLevel automatically record a new workflow version?
On manual save, on publish, and when significant structural changes are detected on the canvas. You can also manually save and name a version at any milestone.
Named versions appear in the sidebar with the label instead of just a timestamp, making specific restore points easier to find.
Make HighLevel workflow edits with the confidence – start your free trial today
Version History, Auto-Save, and Undo/Redo are included on every HighLevel plan at no extra cost. Start your free trial today.
To Wrap It Up
Workflow Version History is one of those features that feels unnecessary until the moment you desperately need it.
The 10-version / 30-day limit is generous enough for most editing workflows. The named version practice closes the gap on complex, heavily edited workflows where the version list fills up quickly.
The three tools – Auto-Save, Undo/Redo, Version History – cover every editing scenario from “I just deleted the wrong thing” to “that rebuild we did three weeks ago broke something.” Getting familiar with when to reach for each one is the main thing.
- Name a version before every major editing session so you always have a labeled restore point rather than hunting through a list of identical-looking timestamps
- Use Create new workflow from version for any significant structural rebuild to keep the original live and untouched during development
- Remember the two restore conditions – Draft mode and no enrolled contacts – so a restore attempt does not fail when you most need it
- Use Undo/Redo for mistakes made in the last few minutes of the current session; reach for Version History for anything older than that
- Filter the Version History sidebar by editor on shared workflows before restoring, to confirm you are recovering the correct state rather than someone else’s recent change
A workflow version history that you never have to use is still valuable – it means you can edit confidently knowing the fallback is always there.