👤 For pipe admins and admin groups.
🔐 Available for paid plans. Version history on Multi-Tenant (MT) and Single-Tenant (ST). Restore on MT only. Both currently in Beta.
🎯 For those who want to keep a record of how a pipe is set up at a given moment, track how it changed over time, and go back to a previous setup when needed.
⏩ Content Summary: Learn how to save and download versions of your pipe's setup, how to restore a previous one, and how to trace them in Activities.
What a version is
A version is a descriptive snapshot of your pipe's entire setup, saved as a JSON file.
It covers 19 kinds of element, including phases, fields, field conditions, automations, conditional expressions, pipe & field connections and more. It does not cover Integrations, APPs, AI Agents for now.
What makes it useful is that it records what each piece is and does, in plain terms, not just internal IDs. That means the file is readable on its own, both by a person and by a tool. A version saves the pipe's configuration, not the cards inside it.
Why this matters
Until now, there was no way to see how a process was configured at a specific point in time. In a complex pipe, reconstructing that from logs alone isn't practical.
"Show me how the credit approval process was set up on March 15th."
If a version was saved on or near that date, download it. The JSON is the complete configuration as it stood.
"What changed in this pipe last quarter?"
Download the version from the start of the quarter and the one from the end, then compare them in a diff tool.
"We're about to restructure this pipe. What if it goes wrong?"
Save a version before you start. You'll have a record of the working setup to compare against and to restore.
"Auditors want documentation of our process configuration."
Each saved version is a dated, readable record of how the process was set up.
"Who saved this version, and when?"
How to access Version history
Open the pipe
Click Manage (top right)
Select Version history
How to create a version
Click Create version. The version will be generated, with a sequential number, Timestamp and who created it. Generation runs in the background, so you can close the panel and keep working. Larger pipes could take longer.
Refresh the page to see the created version. It does not update live for now, once you reload, you'll find the bell notification confirming the version was generated, and the version itself in the list.
If generation fails, you'll see an alert in the panel and no version is added to the list
How to name a version
Versions are created numbered and unnamed so nothing slows down the generation. You can name one afterwards to make it meaningful later.
Find the version in the list
Open the three-dot menu on that row
Select Rename
Type the name and confirm
The name updates in place. You can rename a version as many times as you need.
Naming tip
A good version name answers two questions at once: can I safely go back to this one? and what changed after it?
Combine the state with what came next:
✅ "Stable - before the escalation rework"
✅ "Pre-SLA rollout - working config"
✅ "Approved by IT audit - Aug 2026"
❌ "Version 4", "Backup", "Test"
Six months from now, the number and the date won't tell you which version to download. The name will.
How to download a version
Open the three-dot menu on the version's row
Select Download
You'll get a JSON file structured to be read in any diff tool or hand it to an AI Agent.
How to compare two versions
Comparison happens outside Pipefy for now.
Download the two versions you want to compare
Open both files in a external tool that compares JSON
The tool shows exactly what changed between the two moments
How to restore a version
Restoring replaces your pipe's current setup with the setup saved in a version.
Phases, fields, automations and conditionals all go back to how they were when
that version was created.
📌 For now, only the most recent version can be restored. Older versions
show the action disabled, with a tooltip explaining why. Restoring to any
point in your history is coming.
Open your pipe and go to Manage → Version history.
Find the version you want to restore in the list. Check the date and who created it.
Click Restore.
Read the confirmation dialog and type restore to confirm. The friction is intentional: the action replaces your current setup and can't be undone from the interface.
Wait for the confirmation. The restore takes a few seconds for most pipes, and longer for large ones.
What restoring affects
Your pipe's setup is replaced by the one saved in the version — phases, fields, automations, conditionals.
Cards are not changed, there are some scenarios to consider:
If the restore deletes a phase, the cards are also deleted and don't go to the Trash. This is a limitation from the Trash itself. To restore the cards you'll have to open a ticket with Pipefy support team.
If you restore a previously deleted phase, the cards go to the Trash. Restore the cards from there before creating another version or running another restore.
AI Agents and integrations are not restored. They keep their current setup, which may no longer match the restored structure — review them after a restore.
After the restore
A success or failure alert appears on screen. If the restore fails, your current setup is kept untouched.
All pipe admins get a bell notification (refresh the page to see it) and an email, Restore complete: {pipeName}, with the setup you had before the restore attached as a JSON file. That attachment is your way back if you restored the wrong version.
Tracing a version in Activities
Every version shows a version ID in the list. Creating, renaming and restoring a version are recorded in the pipe's Activities, so you can cross-reference the two.
Go to Manage → Activities → Configuration changes to see who created, renamed or restored a version, and when.
What you can do via API
Create, rename, download and restore a version
All these features via API are available for both ST and MT environments.
📌 API documentation:
https://developers.pipefy.com/reference/create-pipe-snapshot
https://developers.pipefy.com/reference/rename-pipe-snapshot
https://developers.pipefy.com/reference/query-pipe-snapshots