Save and download a version of your pipe's setup

Version history lets pipe admins save a complete record of how a pipe is configured at a given moment — phases, fields, automations and conditions — and download it as a JSON file. Use it to answer what a process looked like on a specific date, and to compare how it changed over time.

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, phase jumps, fields, field conditions, automations and conditional expressions.

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.

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 from via the API.

"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?"

Go to Manage → Activities → Configuration changes. Version creation and renaming are logged with the actor and the timestamp.

Availability: Version history is available on Business and Enterprise plans.

Admin groups have the same access as individual admins.

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

Versions are created numbered and unnamed so nothing slows down the generation. You can name one afterwards to make it meaningful later.

The name updates in place. You can rename a version as many times as you need.

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:

Six months from now, the number and the date won't tell you which version to download. The name will.

You'll get a JSON file structured to be read in any diff tool or hand it to an AI Agent.

Comparison happens outside Pipefy for now.

Every version shows a version ID in the list. Creating and renaming 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 or renamed a version, and when.

Restore is available only via API today: https://developers.pipefy.com/reference/restore-repo-to-snapshot

Restoring from the Version history screen (UI) is coming in a future release.