Overview
This node acts as a manual trigger within an n8n workflow. It allows users to start the workflow by clicking a button, optionally providing custom input data in JSON format. This is particularly useful for testing workflows or running them on-demand with specific input without relying on external triggers.
Practical examples:
- Testing a workflow that processes JSON data by manually supplying sample input.
- Running a workflow interactively during development to verify logic.
- Triggering workflows on demand from the n8n editor interface.
Properties
| Name | Meaning |
|---|---|
| Input | The JSON-formatted data sent when manually triggering the workflow. Optional; if left empty, no input data is passed. |
Output
The node outputs a single item containing the parsed JSON data provided in the "Input" property. The output structure is:
[
{
"json": { /* Parsed JSON object from the Input property */ }
}
]
No binary data is produced by this node.
Dependencies
- No external services or API keys are required.
- No special environment variables or configurations needed.
- This node runs entirely within the n8n environment.
Troubleshooting
- Invalid JSON input: If the "Input" property contains malformed JSON, the node will throw a parsing error. To resolve, ensure the JSON syntax is correct before triggering.
- Empty input: If no input is provided, the node emits an empty JSON object or may throw an error depending on implementation. Provide valid JSON or leave empty if no input is needed.
- Manual trigger not firing: Ensure you click the "Test workflow" or equivalent button in the n8n editor to activate the manual trigger.
Links and References
- n8n Documentation - Manual Trigger Node
- JSON Validator – Useful for validating JSON input before using it in the node.