Templating & Variables

Flows use a powerful templating engine to reference inputs, step results, and helper functions.

Note: In the UI, this may appear as an expression editor.

Context Sources

• inputs: Values provided by form/API/webhook, e.g. { {inputs.searchQuery} }.
• steps: Outputs from previous steps, e.g. { {steps.Search_for_Information.results} }.
• _trigger: Trigger info { type, data }, e.g. { {_trigger.data} }.
• _resumeData: Data supplied when resuming a paused run (wait steps).

Helpers

• str(value): Stringify a JSON object, e.g. { {str(steps.someStep)} }.
• getDate(): Current date/time string.
• currentUser: { name, surname, role, email } when available.

Examples

Prompt with dynamic content

Summarize the following results for { {inputs.searchQuery} } in a { {inputs.summaryLength} } tone:

{ {steps.Search_for_Information.results} }

Final outputs

Define in the Final step:

• Name: summary
• Output: { {steps.Generate_Summary.response} }

HTTP Request payload

{
  "topic": "{ {inputs.searchQuery} }",
  "data": "{ {str(steps.Search_for_Information.results)} }"
}

Tips

• Use descriptive step names; they become keys under steps..
• When including JSON in text fields, wrap with { {str(...)} } to avoid syntax errors.
• HTML entities are decoded automatically before step execution.