Let's Shape The Future Of Your Investments!
Natoque iaculis cursus augue urna commodo aptent morbi tortor porttitor quis ornare.
Short answer: Use the shortcuts shown in your n8n editor. They can save, undo, select, move around the canvas, and open node search. Check the editor before relying on a key combination. Browser, operating system, and n8n version can change the result.
Where to confirm a shortcut in n8n
Open the editor. Find the command, button, or context menu you need. If n8n shows a shortcut beside it, use that as the reference for your installation. This avoids copying a key combination from an older interface.
Use the editor menus when an action is not visible on the canvas. Check the official n8n documentation when behavior depends on a release.
Shortcuts that are useful while editing a workflow
| Task | What to verify in the editor | Why it matters |
|---|---|---|
| Save | The save command and its displayed key combination | Prevents a test or layout change from being lost. |
| Undo and redo | The edit history commands | Lets you reverse a node move, connection, or field change before testing. |
| Copy and paste | The selected-node commands | Useful for duplicating a configured node before changing one parameter. |
| Delete | The delete command for the current selection | Removes the selected node or connection; confirm the selection first. |
| Open node search | The canvas search or add-node control | Finds a node without scanning the full node list. |
| Zoom and pan | The canvas navigation controls | Helps inspect a large workflow without changing its logic. |
How to use shortcuts without changing workflow logic by accident
Before a destructive action, confirm the selected node or connection. A command acts on the current focus. If the cursor is in a field, the key may edit text instead.
Save before a large cleanup. Make one related change. Undo it once. Then redo it if the result is correct. This helps when you move branches or copy a node with credentials and expressions.
After copying a node, inspect its credentials, expressions, and input references. The copy may still point to data used by the original branch.
Testing a workflow after keyboard edits
- Save the workflow and confirm that the intended version is visible.
- Open the changed node and check its parameters and expressions.
- Run a small, known input rather than a full production dataset.
- Inspect the execution result and any error details.
- Return to the workflow editor only after confirming the changed branch behaves as intended.
If an execution fails, use the execution logging and debugging guide. It shows how to inspect the failed node and its input. For a larger workflow, the workflow structure guide covers branches and sub-workflows.
When a shortcut list is not enough
A shortcut can speed up an action. It cannot explain a failed node, a missing credential scope, or an unexpected item shape. Use the node configuration, execution data, and relevant n8n documentation for those questions.
Note the n8n version, operating system, and browser when a shortcut behaves differently. This makes the issue reproducible. It also prevents a local key binding from being treated as a general n8n rule.
