Version History - Workflow Change Control

What is Version History

Version history is an integrated change control system that allows you to save snapshots of a workflow’s state over time. Whenever significant changes are made, you can create a manual version or the system automatically creates backup versions.

It works as a change control system that lets you:

Roll back if a change breaks functionality
Compare two versions to see what changed
Audit the evolution of a workflow over time
Recover lost or accidentally deleted work

Version Types

Automatic versions (Auto)

The system automatically creates versions whenever a workflow is saved. These versions appear with the Auto label and serve as restore points without user intervention.

Manual versions

Manual versions are created explicitly from the History panel. They allow you to add a description explaining the change, making them ideal for marking important milestones (e.g., “Before changing payment flow”, “Stable version v1.2”, etc.).

Accessing the History

Open a workflow in the visual editor
Click the History icon in the editor’s top toolbar
A right side panel will open with all saved versions

Each history entry shows:

Version number (v1, v2, v3…)
Type (Auto or Manual)
Date and time of creation
Number of nodes and connections in that version
Description (if it was a manual version)

Create a Manual Version

In the History panel, click Create Version
(Optional) Add a description of the change
Click Create

The new version will be added to the top of the list with the Manual label.

Compare Versions

The comparison feature lets you see exactly what changed between two versions of a workflow.

How to compare

In the History panel, click on a version to select it (it will be marked with an orange border)
Click on a second version
Press the Diff button

What is compared

The system performs a deep analysis of changes between the two versions. It compares:

Aspect	Detail
Added nodes	Nodes that exist in the newer version but not in the older one
Removed nodes	Nodes that existed in the older version but no longer exist
Modified nodes	Nodes whose complete configuration has changed
Added connections	New connections (edges) between nodes
Removed connections	Connections that no longer exist

What does a “modified” node include

A node is marked as modified when any part of its configuration has changed. This includes:

Node variables (name, type, default value)
Scripts (JavaScript code, expressions, formulas)
Configuration parameters (URLs, headers, messages, etc.)
Selected credentials
Database connections or external service connections
Any other property defined in the node’s config object

Current Limitation

Currently the system reports that a node changed, but does not show a line-by-line diff of internal changes. To see specific changes, use the Preview of each version and visually compare the configuration.

Restore a Version

If you need to revert to a previous version:

Locate the version in the History panel
Click the Restore icon (circular arrow)
Confirm the action

Important: Before restoring, the system automatically creates a backup version of the current state, so you can undo the restoration if it was a mistake.

Preview a Version

If you want to see the contents of a version without restoring it:

Click the Preview icon (eye) on the version
A dialog will open showing:
- Metadata (date, type, number of nodes and connections)
- JSON preview of the workflow

From the preview you can also restore the version directly.

Delete a Version

Click the Delete icon (trash) on the version
Confirm the action

This action cannot be undone. You cannot delete the only remaining version of a workflow.

Best Practices

Create manual versions before large or risky changes
Use clear descriptions to easily identify each version
Compare versions before restoring to understand the changes
Don’t rely only on automatic versions for critical changes
Clean up old versions you no longer need to keep the history manageable