Node reference
Manual trigger node
manual_trigger · Updated September 17, 2026
Every workflow starts with exactly one trigger. The Manual Trigger runs the workflow from the editor with test inputs you fill in on the node: one name and value per row, no JSON needed.
When to use it
- While building and debugging any workflow.
- For workflows you run on demand, such as a report you draft when needed.
Ports
- Inputs
- None
- Outputs
out
Configuration
- Test inputs
test_payload - objectValues your prompts read as {{ trigger.<name> }}. An attached PDF arrives as {{ trigger.file }}.
Output
Fires out with the test inputs. Every node downstream can read each one as {{ trigger.<name> }}. Any variable a prompt already reads appears as a row for you to fill in, and JSON switches the rows to a raw object.
Example
{
"customer": "ann@example.com",
"message": "I was charged twice",
"urgency": "high"
}Keep reading
- Webhook trigger nodeThe Webhook trigger starts a Worfilo workflow from an HTTP request. The node exists today; the public webhook endpoint is on the roadmap.
- Getting started: build your first AI agent workflowGet started with Worfilo: create an account, connect your apps and APIs, then generate or build your first AI agent workflow and watch it run live.
- Templates and expressions: pass data between nodesPass data between workflow nodes with Jinja templates: read run inputs and upstream outputs, branch on expressions, and keep raw values intact.
Build it on the canvas
Create a free account, describe the workflow or wire it yourself, and run it in the browser.