Open command palette
A universal keyboard entry point that gets used constantly.
With MacKeys
Without MacKeys
Automation shortcut guide
n8n belongs in the MacKeys directory because building and editing automations often happens in long, keyboard-first sessions. This page focuses on the shortcuts that are most worth preserving across Windows and macOS.
With MacKeys
The goal is not to make Figma different. It is to remove the modifier translation layer so common actions still feel like the Mac workflow your hands already know.
Without MacKeys
Native Windows shortcuts usually ask for `Ctrl` and `Alt` translations. In dense design sessions, that adds up as hesitation, extra reach, and slower recovery when you are moving quickly.
Shortcut rows
8
Workflow actions covered on this page.
Translated shortcuts
8
Rows where MacKeys removes the Windows modifier translation.
High-gain actions
2
5 of these are high-frequency shortcuts.
Workflow sections
Jump to the part of Figma where shortcut translation matters most.
Workflows
Workflow shortcuts used frequently in n8n.
A universal keyboard entry point that gets used constantly.
With MacKeys
Without MacKeys
A repeated action that benefits from consistent modifier patterns.
With MacKeys
Without MacKeys
Editor
Editor shortcuts used frequently in n8n.
A common visibility toggle in many keyboard-heavy apps.
With MacKeys
Without MacKeys
A frequent action in most workflows where speed matters.
With MacKeys
Without MacKeys
Runs
Run and execution shortcuts used frequently in n8n.
A simple but frequent app-level access pattern.
With MacKeys
Without MacKeys
A core browser-and-editor shortcut that users expect immediately.
With MacKeys
Without MacKeys
Reading the gain labels
A shortcut gets a higher estimated gain when it combines three things: frequent use, more awkward native Windows modifiers, and a higher likelihood of breaking Mac muscle memory in the middle of focused work.
Why this matters in n8n
n8n rewards fast repetition. Duplicate, group, frame, zoom, and property-copy actions are not isolated commands. They are part of the rhythm. The closer that rhythm stays to Mac muscle memory, the less time gets lost to tiny modifier decisions.
FAQ
Because it runs on both macOS and Windows and supports a workflow where keyboard speed matters.