Action Flow Parameters

Sometimes you want to run the same behavior in many places with slightly different values. For example, a "go to detail screen" flow is always the same, but which item's detail it shows differs each time.

Parameters let an Action Flow receive values from the outside at the moment it runs. This lets you reuse a single flow across many situations.

Defining Input Parameters

You define the shape (Schema) of the input parameters on an Action Flow. The flow then receives data of that shape when it runs. Inside the flow, you can reference these values with the {Parameters.field} token.

Injecting Values: Binding Sources

The caller connects the actual values. Values can come from three scopes:

• Project — Data shared across the entire project
• Page — Data belonging to the current screen
• Cell — The item data corresponding to each individual List cell

For example, if you call a detail-navigation flow from a List cell's Touch event and inject that cell's item data (Cell) as the parameter, you can navigate to the detail screen for the item that was tapped.

API Input Parameters

APIs have input parameters in the same way. The API Call action injects the connected input data into the API, and the API uses those values in its URL, headers, and body via the {Parameters.field} token. (See Binding API Responses to UI)