DocumentationWorkflowsTriggers
Manual Trigger node
Starts the workflow when you click Run. Your JSON input is passed through unchanged. Following steps read its fields directly from $json, for example $json.message. Learn how to configure it, map inputs and outputs, run a test and resolve common errors.
7 min readUpdated
What this node does
Starts the workflow when you click Run. Your JSON input is passed through unchanged. Following steps read its fields directly from $json, for example $json.message.
Use Manual Trigger as a clearly defined step in an anymize workflow.
- Starts a new workflow run.
- Provides one output for following steps.
- Runs as a regular step in the flow.
Set up the node
- 01Open a workflow and add Manual Trigger from the node catalog.
- 02Complete the required fields and map values from previous steps.
- 03Run the node with a small test record and inspect its output.
- 04Connect the successful output and activate the workflow after an end-to-end test.
Operations and modes
Manual Trigger has one focused purpose. Its available settings appear when you select the node.
Settings
This node has no persistent configuration. Its data comes from the trigger or previous step.
Inputs and outputs
| Input | Meaning | Type |
|---|---|---|
| Standard | This trigger does not require an input. | JSON |
| Output | Meaning | Type |
|---|---|---|
| message | Example input field. Available when your run input contains a message field. | text |
| user_id | Example input field. Available when your run input contains a user_id field. | text |
Example and test run
Example run input: begin with a small, recognizable record. Inspect the output and only map fields that are present there.
Test-run example
{
"message": "Hallo Welt",
"user_id": "dev-42"
}Access and security
Before activation, review which data enters this step and what its output contains.
Store keys and credentials in the protected connection manager. Never paste them into normal workflow fields, test data or descriptions.
Troubleshooting
- No output: inspect the latest run and confirm that the previous node returned the expected fields.
- Empty variable: open the previous step output and use a field name from the real test data.
- Workflow does not start: activate it and check the trigger's test and production mode.