On this page
What HubSpot supports natively
| Action | What it changes | What it leaves alone |
|---|---|---|
| Delete the workflow | The workflow moves to the Deleted tab for 90 days | Every change it already made to records |
| Turn the workflow off | No new enrollments; actions other than delays are skipped | Changes already made |
| Unenroll a record | Stops future actions for that record | HubSpot: it “does not undo actions that have already executed” |
| Restore workflow CRM property changes | Reverts CRM property changes one workflow made in a chosen date range | Changes older than 14 days, changes made by other workflows it triggered, and changes from custom-coded actions |
| Restore CRM changes | Rolls records back to a point within the last 14 days, including workflow updates | Older changes |
| Record property history | Restore a value on one record when the source was a workflow, import or CRM edit | Other records |
The workflow-level restore needs an Enterprise subscription and Super Admin permissions. It restores every eligible update from the selected runs, including ones you may want to keep, and HubSpot recommends turning the workflow off first.
Sent emails, notifications and webhooks can’t be taken back by any of these tools.
How to undo the changes a workflow made
- Turn the workflow off first so it stops making new changes. Don’t delete it yet: the restore tool starts from the workflow’s enrollment history.
- Work out the scope. Which properties, which records, which dates. A saved view filtered on the property and last-modified date helps.
- If it’s within 14 days and you’re on Enterprise, open the workflow’s Enrollment history, click Restore CRM changes, prepare a preview, review the records, and restore.
- If another workflow was triggered by the bad one, restore that workflow’s changes separately.
- If it’s older than 14 days, rebuild the old values from property history or a backup and re-import them. Test on a few records first.
- Fix the workflow, using revision history to see what changed and who changed it, then delete it or turn it back on.
Common mistakes
- Deleting first. You lose the easiest route into the enrollment history and the restore preview.
- Assuming unenroll means undo. It only stops what hasn’t happened yet. See how to unenroll records.
- Restoring too much. A restore covers all eligible updates in the run, including correct ones made by the same workflow.
Where Jetstack AI fits
Jetstack AI doesn’t undo HubSpot workflow actions or record updates; use HubSpot’s restore tools above for those. Its rollback covers Portal reuse deployments only: you can roll back a Portal reuse deployment: Jetstack shows you what will be removed first, then deletes the assets that deployment created in the destination portal. It won’t delete anything another deployment or Project still uses, and it skips assets that were changed after the deployment. See rolling back a deployment.
Sources
- Delete and restore workflows (HubSpot Knowledge Base)
- Restore workflow CRM property changes (HubSpot Knowledge Base)
- Restore CRM changes (HubSpot Knowledge Base)
- Manually unenroll records from workflows (HubSpot Knowledge Base)
Checked October 29, 2026. HubSpot changes its products often; tell us at team@jetstack.ai if something here is out of date.
Workflows & automation
Take a proven setup to the next portal.
Import a setup with its dependencies, map it to the destination portal and deploy it with references rewritten.
Explore Portal reuse