Undo & Redo
Cmd+Z / Ctrl+Z takes back your last change, and Cmd+Shift+Z / Ctrl+Shift+Z puts it back again. That covers a deleted step, a mistyped field, or a whole branch the Workflow Assistant generated.
This page covers what undo reaches, how the history is kept separate per tab, and what happens when a colleague is editing the same canvas.
What undo covers
Undo reaches further than moving and deleting steps.
You can undo and redo:
- Canvas Movements: Dragging steps, drawing connection links, or reorganizing the layout.
- Drawer Configurations: Typing into input fields, mapping variables, or changing step settings inside the right-hand App drawer.
- Agentic Changes: If the Workflow Assistant generates a 10-step branch you don’t like, a single
Cmd+Zreverts it. That covers the steps and the connections between them.
Check the settings on a step the Assistant configured for you. Where it worked out a value on its own (picking the channel, selecting the sheet), that value can survive the undo. The step around it is still reverted. Undo takes back the structure reliably. Treat the contents of a step it configured as worth a look rather than assuming they went with it.
One action, one press
Some actions touch several parts of a workflow at once. Clear all props on a step, for example, changes both its plain fields and any field you mapped a variable into. These are reversed as a single action: one Cmd+Z brings all of it back, not half of it.
Part of such an action may no longer be reversible, because you closed the drawer it belonged to, say. The whole action is then skipped rather than half-applied. The press falls through to the most recent action that can still run.
Tab-Specific Context
Each tab keeps its own undo history, so workflows open side by side in Canvas Tabs never share one.
Say you make three changes in “Workflow A”, switch to “Workflow B” to edit a webhook, then switch back. Hitting Cmd+Z undoes only the changes you made in “Workflow A”.
An undo never reaches into a workflow open in another tab. Each tab keeps its own history while you move between them.
Multiplayer safety
Your undo history is your own. Press undo and you take back your last action, never one belonging to a colleague editing the other side of the canvas.
So an undo in a shared workflow only ever reverses something you did. You do not have to check who has touched the canvas since your last change.
What’s Next?
- Roll back further than the undo stack reaches with Versioning.
- See how per-user history works alongside teammates in Real-Time Editing.