Skip to main content
Node type: manual_trigger · Version: 1 · Category: Triggers Run from the toolbar. 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

  • Build and debug a workflow before choosing an automatic trigger.
  • Run an operator-led task where a person should decide exactly when work starts.

​
Example: Test a website health check

Use a Manual Trigger while building a flow that requests a health endpoint and branches on the returned status.
  1. Add Manual Trigger as the first node.
  2. Connect it to HTTP Request, then map the response status into Condition.
  3. Run from the toolbar and inspect every node before replacing the trigger with a schedule.

​
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 trigger emits the run event and execution context; it does not accept input data.
  • Starting another run still follows the workflow’s concurrency and queue settings.
  • The editor catalogue declares event (object) 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 Run is unavailable, complete validation errors elsewhere in the workflow.
  • A manual start does not bypass permissions for downstream network, file, command, browser, or communication nodes.

​
Where it can run

  • Desktop local runner
  • Paired self-hosted runner
  • Hosted runner

​
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.