Reference · Tools
Manual Trigger node
Starts a workflow execution when the user clicks the Execute button. This trigger type requires no external events and is used for on-demand execution.
Manual Trigger starts a workflow when you click Execute, emitting one item carrying a timestamp so the nodes after it have something to process. It needs no credentials and no configuration. It is the entry point for anything you run on demand rather than on a schedule or an external event.
- Works as
- Manual trigger
- Tool name
manual_trigger- Parameters
- 0
- Outputs
- Output
- Credentials
- None required
What you can build with Manual
- Start the workflow manually.
- Run this workflow on demand.
- When execute when I click the button.
Overview
Starts a workflow execution when the user clicks the Execute button. This is the simplest trigger type — it requires no external events.
Node Type
Trigger — manual (starts the workflow when you click Execute)
Input / Output
| Direction | Port(s) |
|---|---|
| Input | None (trigger node) |
| Output | Output |
Credentials
This tool does not require any credentials.
Parameters
This node has no parameters to configure.
Output Data
Emits exactly one item so the nodes downstream have something to run on:
_trigger— alwaysmanual_timestamp— ISO 8601 timestamp of when the run started
Reference it downstream by expression, e.g. {{ $json._timestamp }}.
Example Configuration
Add the trigger and connect it to the first node of your workflow:
{
"type": "manual_trigger",
"parameters": {}
}Trigger Behavior
- Activation: None required — the node runs whenever you execute the workflow yourself.
- Payload: Emits a single item so downstream nodes have something to process.
- Use: Building and testing a workflow before attaching a real trigger.
Tips
The Manual Trigger starts a workflow execution. This tool is ideal when a workflow needs to be initiated by a user’s direct action, rather than by an external event or schedule. It produces a single item containing a timestamp, which can then be processed by subsequent nodes.
Frequently asked questions
What does it actually output?
A single item with a timestamp. That is enough to start the chain — most workflows immediately fetch or generate their real data in the next node.
Can a manually triggered workflow also be scheduled?
A workflow starting from a Manual Trigger is eligible for scheduling, so the same workflow can be run on demand and on a cadence.
Does it need any configuration?
None — it has no parameters and no credentials. Drop it in and connect the first real node.
When should I use a different trigger?
When the workflow should start without you: a webhook trigger for inbound events, a polling trigger to watch an external system, or a schedule for time-based runs.
Build with the Manual Trigger node
Drop it into a workflow, wire it to an agent, or call it on a schedule.
Open BusyBotLast reviewed . Spotted something wrong? Tell us.