Skip to main content
Node type: press_key · Version: 1 · Category: Browser Send a validated key combination. This node is not marked with the catalogue’s generic side-effect flag. That classification is not a guarantee that every configured operation is read-only; review the concrete action and its destination.

​
When to use this node

  • Submit a form with Enter, dismiss a dialog with Escape, or use a supported shortcut.
  • Trigger keyboard behavior when clicking is not equivalent.

​
Example: Submit search with Enter

Run Press Key immediately after filling the focused search field.
Example settings
This shows the important settings, not a complete exported node.
  1. Ensure the preceding action leaves focus on the intended control.
  2. Enter a validated key or key combination.
  3. Wait for the resulting navigation or element state.

​
Configuration

​
Workflow JSON

The editor stores this node with the following implemented default configuration:
Default node configuration
Values may be entered literally or mapped from an earlier compatible output when the inspector exposes a mapping control. See Variables and data mapping.

​
Inputs

This node has no typed ports in this direction.

​
Outputs

​
Execution behavior

  • The key is sent to the active page using the current focus context.
  • The timeout bounds dispatch and browser response, not all work started by the shortcut.
  • The editor catalogue declares result (any) for mapping. The execution inspector can contain additional evidence fields; inspect a real result before selecting nested paths from object or any outputs.

​
Common issues

  • If focus moved, the page or wrong control may receive the key.
  • Operating-system shortcuts and application-level browser shortcuts are not the same as page keyboard input.

​
Where it can run

  • Desktop local runner
  • Paired self-hosted runner
  • Managed browser worker

​
Test and inspect

Use Test node in the editor to preview this step with the current configuration. A full run records resolved inputs, outputs, logs, duration, and any artifacts in the execution inspector. Side-effecting or destructive nodes can require an additional confirmation or approved workflow permission.