Read workflow input

Emit the records the run was invoked with, unchanged.

Emit the records the run was invoked with, unchanged.

When to use it

Start a process with the records supplied when the run was invoked. This step passes them through unchanged. An invocation with no records has no input rows to process unless another source supplies them.

Add and configure

1. Add Read workflow input from the workflow step picker.
2. Give the step a recognisable name and connect its required inputs.
3. Set the options below. Nested names identify fields within an object or a list item.
4. Validate the recipe, inspect the test result, then run it on the intended data.

The step identifier used in the editor’s code view is read_input.

Settings

This step has no declared configuration fields.

Inputs and outputs

Effects, testing, and recovery

Transforms or passes records without a declared external side effect.

The declared preview behaviour is to execute this step. Reads, processing, or model usage can therefore be real. Read dry runs before using a preview with live connections.

No duplicate-prevention key is declared for this step. The step declares safe replay for its supported recovery path.

Example: Pass the run's supplied records through

Step settings:

{}

Input records:

[
  {
    "id": 1,
    "name": "Ada"
  },
  {
    "id": 2,
    "name": "Grace"
  }
]

Expected output for this example:

[
  {
    "id": 1,
    "name": "Ada"
  },
  {
    "id": 2,
    "name": "Grace"
  }
]

Example: An empty input stays empty — nothing is invented

Step settings:

{}

Expected output for this example:

[]

Check the result

Inspect the selected run’s status, counts, errors, and output records. An empty collection can be a valid result, and a completed step can contain per-record failures where the step defines that behaviour. Check the next step’s expected record shape before publishing or delivering the result.