Overview
Version history lets you save and download any pipe's setup directly in Pipefy. It helps IT governance teams see how a process was configured on a specific date and provides a record for safer adjustments before high-risk operational changes.
What's new?
- One-click version creation: save a version of your pipe's setup under Manage → Version history. You can rename each record to make it easier to identify.
- JSON file download: download a version's JSON file to inspect the setup, compare configurations from different points in time with a diff tool, or share it with an AI agent.
- Completion notification: receive an in-app notification confirming that processing is complete and the version is ready in the list. The notification appears when you refresh the page.
- Pipe traceability: view each version's ID, author, and date, with events automatically recorded in the history under Activities.
How does this help?
- Record a stable process setup before editing the pipe: save a reliable checkpoint before restructuring the pipe, giving you a reference for comparison and adjustments if needed.
- Track the process over time: each saved version becomes a point in the pipe's history. You can see how it was configured on any date for which a version exists, without relying on memory, reconstructing it from logs, or opening a support ticket.
Use cases
- Record a stable process setup before editing the pipe: Before changing the phases and conditionals in a critical pipe, an analyst saves a version and names it "Pre-SLA setup." A visibility rule breaks during testing. The analyst downloads the saved version's JSON, compares it with the current setup using an AI agent or a diff tool, finds the field that differs, and fixes it in minutes.
- See how the process was set up on a specific date: The credit team saves a version whenever an approval rule changes. Months later, the IT governance team asks how the workflow was configured on March 15. The Pipe Admin opens version history, finds the version from that date, and downloads the file. With that record, they can communicate the exact rules in effect at the time without reconstructing them from logs or opening a support ticket.
Most relevant for
- Pipe Admins
- IT Leaders
- Operations teams
- Builders
Documentation
For the full step-by-step, check the Help Center article.
Plans and availability
This feature is available on Business and Enterprise plans in Multi-Tenant (MT) and Single-Tenant (ST) environments. Access is restricted to Pipe Admins.
Saved versions include the pipe's setup (phases, automations, fields, and other elements), but not its cards. Integrations, APPs, and AI Agents are not currently included.
Restoring a pipe to its latest saved version will be available in the UI soon. For now, restoration is available through the API. Check out this update to learn more about what you can do via the API.
