Pass States

The Pass state ("Type": "Pass") passes input to output and does no work.

Pass states may contain a ResultPath, a JSONPath expression indicating where the input should be placed in the output from the state. If given an InputPath, a Pass state takes its input from a particular location in the flow’s current data.

Pass states may also contain a Result, containing static output data.

Pass states are also useful as terminal success states, for example after a Choice state.

Fields

The following fields are the valid parameters to a Pass state.

InputPath: A JSONPath expression, indicating a source in the flow's current data. This is most useful when combined with ResultPath.
ResultPath: A JSONPath expression, indicating a source in the flow's current data. This is most useful when combined with ResultPath.
Result: A static payload to use as the state output.
Next: The string name of the next state.
End: If set to true, the flow terminates with a success upon reaching this state.

Either "End": true or Next must be set.

Examples

This Pass state puts all of the input data into the field named "Nested", then transitions to the state named "AfterPass":

{
  "Type": "Pass",
  "ResultPath": "$.Nested",
  "Next": "AfterPass"
}

This is a simple successful end state for a flow, phrased as a Pass:

{
  "Type": "Pass",
  "End": true
}