You can inject variables from the context stack into the step inputs.


You can inject variables in the steps inputs as a result from another steps. That’s Context. There are many cases that shows you the context utility. For example, when you want to update a record from data that is output by a previous create-record step. You can log the error result by a try-catch step or may you want to create a record from actions’ parameters data.

Context Stack

How to add items to the context stack

There are some steps that can outputs their results into the Flows’ context execution, e.g. the createRecord step outputs the created record. All those outputs are put in the context stack if you select put in context. The context stack may contain default items depending on where the Flow is executed from, e.g. if it is executed from an action you can see the actions’ parameters in the context stack.

How to use items from the context in the inputs

By default, an input is meant to accept a fixed value. Some inputs can accept a value from the context. In those, you can select a value from the context according to its scope.


Every item in the context stack has its scope. Context items are only available if you are editing a step that is forward or inside the step that output the context item. For example, you can not select context items from steps that are outside from the step that output to the context. Neither select an output from a step that is before in the execution flow from the step that output to the context.


Context stack example
In the updateRecord step inside a tryCatch step, cannot access to findData output because is not forward to findDatas' execution flow. In the other hand, he can access to super steps output: tryCatchError .
Back to top