Skip to main content

Using data in workflows

Each step receives the values its configuration selects. A fixed value stays the same across runs. A mapping reads a value from the trigger or a preceding step. For example, a Task title can combine **Review request: ** with the triggering record's display name.

Captured values and later observations​

Trigger values belong to the captured input of that run. If someone renames a record while the workflow is waiting, an existing trigger mapping still uses the captured name.

To observe the record later, add Read Record and select the fields you need. Its accepted result becomes a separate output. Recovery reuses that result rather than silently reading a newer value again.

Available outputs​

The editor offers values according to their declared type and their position in the graph. Scripts and Agents have published output contracts; record actions expose selected record data; Ask Question exposes its interaction outcome. Control steps such as Join and End do not invent data outputs.

A value may come from any step that precedes its consumer on at least one path. After a Join, you can select values from either earlier branch. If the selected source did not run, its value is null, or the binding's default when configured. Choose a destination that accepts null or supply a compatible default. Steps on an unrelated path, the current step and later steps are unavailable. Trigger values remain available throughout the workflow.

Missing is different from empty​

For Script and Agent input bindings:

Source valueResult
Present and compatiblePassed to the selected input.
Source step skipped on the taken pathThe binding default is used when configured; otherwise the value is null.
Missing optional property, with a valid defaultThe default is used.
Missing optional property, without a defaultAn optional destination is omitted; a required destination needs a guaranteed value.
Explicit null, empty text, false or zeroRemains that value. A default does not replace it.

Types are checked at publication and execution. A text destination does not automatically convert a number, and a Wait timestamp needs a declared date/time value from a source that runs on every path. Record IDs and upsert keys also require a source that runs on every path. A skipped source mapped into a nullable record attribute clears its existing value; omit the attribute or place the write inside the branch to preserve it. Record writes and Task titles have their own field rules; do not assume every input supports defaults.

Scripts and Agents receive explicit inputs​

A new inline Script can initialize inputs from the preceding step's declared output. Review those mappings, especially after graph changes. Copying a workflow version preserves its steps’ input contracts. Agents require explicit input selection. No bindings means an empty payload; the whole record is not automatically sent to a model.

Preview can resolve captured values and conditions, but cannot produce actual Script, Agent or record-action results. See Scripts and Agents API mappings for exact binding rules.