Automation Version History
View and restore previous automation versions
Automation Version History
Mailnaptic automatically tracks changes to your automations, creating a version history that lets you see what changed and when. If an update causes problems, you can restore a previous version to quickly recover.
How version history works
Every time you save changes to an automation, Mailnaptic stores a snapshot of the automation's state. This includes:
- The complete node structure (all steps and their configuration).
- Edge connections between nodes.
- Trigger configuration.
- Email content within send email steps.
- The timestamp of the save.
Each snapshot becomes a version in the automation's history.
Viewing version history
- Navigate to Automations and open the automation.
- Look for the Version History option in the automation editor or detail page.
- The history displays a list of all saved versions with timestamps and a summary of changes.
Comparing versions
Click on any version to preview its state. You can see:
- The automation flow as it existed at that point in time.
- Which steps were present, their order, and their configuration.
- Email content that was in use at that version.
Compare the previous version against the current version to understand what changed.
Restoring a previous version
- Open the version history and find the version you want to restore.
- Click Restore on that version.
- The automation's flow and configuration are reverted to the selected version.
- A new version entry is created for the restore action, so you can always undo the restore if needed.
Important: Restoring a version does not affect contacts who are currently in the automation. They will continue from their current step in the restored flow. If the restored version has a different structure (missing steps, different branching), contacts at affected steps may need manual attention.
When to use version history
- Accidental changes: If you accidentally delete steps or misconfigure a condition, restore the previous version.
- Performance regression: If engagement drops after an automation update, compare versions to identify what changed.
- Audit trail: Track who made changes and when for compliance or team coordination.
- Safe experimentation: Make bold changes knowing you can always revert if they do not work out.
Best practices
- Save frequently while editing to create granular version history.
- Deactivate the automation before restoring a version, especially if the structure has changed significantly.
- After restoring, review the automation flow carefully and test before reactivating.
- Use version history alongside duplication — duplicate before major changes as a belt-and-suspenders approach.
Version history provides a safety net for automation management, giving you confidence to iterate and improve without fear of irreversible mistakes.