Result
Captures the run's answer: the value whatever waited on this automation reads once the run completes. Reach for it in an automation that other automations call and wait on, that an Automation Completed trigger listens to, or that an AI agent calls as a tool. For the whole picture, see Results and MCP tools.
Fields
| Field | Description |
|---|---|
| Value | The answer. Choose Variable to pass an object an earlier step built, or Object to build one here field by field, the way the Automation action builds a payload. It must match the Result declared in the automation's settings; the form lists the Result's fields and warns while a required one is missing. Left empty, the answer is an empty object. |
What later steps see
The answer, shaped as the declared Result, so a step after this one can read it like any other output.
Behaviour
The automation has to declare a Result in its settings first; without one, the step fails and says so. The value is held to that Result when the step runs, and one that does not fit fails the step with a message naming what is wrong.
A run keeps one answer. The first Result to complete gives it, and any Result that runs afterwards fails, naming the one that answered. Join branches before a single Result, and put a Result after a Loop End rather than inside the loop, where it would answer on the first iteration and fail on the next. The failure is a step failure like any other, so an error path from the step handles it.
The answer is captured here and delivered when the run completes. Every step after this one still has to succeed, and a step that pauses for a person holds the answer until they act.