Chat To ClientsHelp Center

How can we help?

Knowledge baseWorkflowsWorkflow Builder

Workflows: Version History & Restore

UseTrack, compare, and roll back workflow edits with ease. The redesigned Version History to review sidebar, one-click restores, and smart version labeling give you total confidence while building automations—all without extra cost.


TABLE OF CONTENTS


What is Workflow Version History?


Version History is Chat To Clients CRM’s built-in timeline of every saved state of your workflow. Each entry records who edited it, the exact time stamp, and whether the version was a draft or published build. With the 2025 revamp, you can browse, filter, and restore past versions of a workflowin seconds, eliminating guesswork and restore any version as a new draft, your live workflow doesn’t change until you Publish. This follows the same draft → publish model used across Workflow.risky re-builds.


Key Benefits of Workflow Version History



Use Version History to review past versions of a workflow and restore any version as a new draft, your live workflow doesn’t change until you Publish. This follows the same draft → publish model used across Workflow.


What’s included


Version History Revamp



Restore Previous Versions



Enhanced Browsing Experience




How Version History is created


Version History automatically records versions at key moments:


Auto Save note: routine auto-saves do not create new versions by themselves.
To capture your current state as a version, click Save Version—this snapshots your latest auto-saved changes into Version History.




Unsaved changes confirmation


Browse versions


Open Version History to see your saved entries, organized by time and editor.

Each entry shows:




Version list



You can:


Restore or create from a version



Restore / create new workflow



When restoring:



How Workflow Changes Effect Contacts Already in Progress


Contacts already progressing through a workflow can use updates made to upcoming actions.


For example, if a contact is currently in a Wait action and you update an action that comes after it, the contact uses the updated action when it reaches that step. If you add a new action after the Wait action, the contact can also execute the new action as part of the same workflow journey.


Changing the Wait action itself does not update the existing wait for contacts already in that step. Those contacts complete their current wait before continuing through the updated workflow.


Best practices



Notes & limitations


Last updated Thu, 10 Sep, 2026 at 6:16 AM