Output node
The workflow's endpoint. Collects the final result. Learn how to configure it, map inputs and outputs, run a test and resolve common errors.
6 min readUpdated
What this node does
The workflow's endpoint. Collects the final result.
Use Output as a clearly defined step in an anymize workflow.
- Processes one input.
- Ends the connected path.
- Runs as a regular step in the flow.
Set up the node
- 01Open a workflow and add Output 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
Output 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 |
|---|---|---|
| result | The workflow's final result. | any |
| Output | Meaning | Type |
|---|---|---|
| Standard | Ends this path without another output. | JSON |
Example and test run
Terminal, no input needed: begin with a small, recognizable record. Inspect the output and only map fields that are present there.
Test-run example
{}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.