Overview
The node serves as the starting point for manual workflow executions in n8n. It does not perform any data processing or transformation itself but acts as a trigger to initiate the workflow when a user manually executes it from the canvas. This node is essential in workflows that require manual initiation rather than automatic triggers.
Practical example:
You design a workflow that sends notifications or performs data updates only when you explicitly start it. Placing this node at the beginning allows you to control exactly when the workflow runs by clicking "execute workflow" on the canvas.
Properties
| Name | Meaning |
|---|---|
| notice | A static informational message indicating that this node is where manual workflow execution starts. |
Output
- The node outputs the input data it receives, which is typically empty since it has no inputs.
- The output JSON structure is essentially an empty dataset or the initial data passed into the workflow.
- No binary data is produced by this node.
Dependencies
- No external services, API keys, or environment variables are required.
- This node relies solely on n8n's internal mechanism to start workflows manually.
Troubleshooting
- Common issue: Users might expect this node to process or transform data, but it only triggers workflow execution.
- Error messages: None specific to this node, as it does not perform operations that can fail.
- Resolution: Ensure that the workflow is executed manually via the canvas interface to trigger this node.
Links and References
- n8n Documentation - Start Node (for general understanding of the start node concept)