Hotkey
Hotkey
Section titled “Hotkey”Run the flow from a keyboard shortcut.
What it does
Section titled “What it does”Triggers workflow execution when you press a keyboard shortcut, so a workflow can run from anywhere in the browser without opening a menu.
When to use it
Section titled “When to use it”Use this trigger for workflows you run often and want instant, keyboard-driven access to.
Inputs and settings
Section titled “Inputs and settings”| Setting | Notes |
|---|---|
| Hotkey Slot | The keyboard-shortcut slot this trigger listens on (run-workflow-1 … run-workflow-4). Source-backed field from the node schema. |
Choosing a slot and assigning the key
Section titled “Choosing a slot and assigning the key”Chrome only lets an extension declare a fixed set of keyboard commands in its manifest — you cannot register an arbitrary shortcut per workflow at runtime. The extension therefore ships four generic slots (Hotkey slot 1–4). In the node, pick which slot should fire this workflow.
Then assign the actual key combination at:
chrome://extensions/shortcutsFind “Agentic Workflow”, locate the slot you chose (for example “Run workflow bound to Hotkey slot 2”), and set your key combo there.
The Chrome shortcut cap
Section titled “The Chrome shortcut cap”Chrome limits how many shortcuts an extension may suggest by default (currently four, of which we suggest a default for slot 1 only — Ctrl+Shift+1 / Command+Shift+1). The remaining slots start unbound: they will not fire until you assign a key combination to them at chrome://extensions/shortcuts. If a hotkey does nothing, this is almost always the reason.
Outputs
Section titled “Outputs”Starts the workflow and passes the fired command name (triggerType: "hotkey", command, triggeredAt) to downstream nodes.
Dependencies and credentials
Section titled “Dependencies and credentials”- Requires the extension’s
commandspermission (declared in the manifest). - No external credential is declared in the node description.
Example workflow
Section titled “Example workflow”Create a workflow with Hotkey as the first node, choose a slot, assign its key combo at chrome://extensions/shortcuts, then connect it to the action nodes that should run after the shortcut fires.
Troubleshooting
Section titled “Troubleshooting”- If nothing happens, confirm the slot you selected in the node has a key combo assigned at
chrome://extensions/shortcuts. - Make sure no other extension or the browser itself already claims the same key combination.
- Two workflows may listen on the same slot; both will run when that slot’s shortcut fires.
- This node has source tests; use them as the reference for edge-case behavior during maintenance.