Understanding how data flows through your workflow and how to reference it is essential for building sophisticated automations. Variables make data available from one step to the next.
Variable Syntax
All variables follow a consistent pattern:
@StepType.OutputFieldName or @SpecificStepName.OutputFieldName
Variable Sources
Intake Variables
Data collected in the Intake step is available throughout the flow:
- Free-text:
@Intake.Message
- Form fields:
@Intake.FieldName (e.g. @Intake.CustomerName, @Intake.ContractTerm)
Step Output Variables
Outputs defined in Agent steps are available as @AgentStepName.OutputFieldName. For example, an Agent step called “RiskAnalysis” with an output “RiskLevel” is referenced as @RiskAnalysis.RiskLevel.
Collect Step Variables
Information gathered in Collect steps is available as @CollectStepName.FieldName.
Data Flow Examples
Free-Text Flow
Form-Based Flow
- A Slack mention is captured as
@Intake.Message
- An Agent step analyzes the message and outputs
@AgentStepName.OutputName
- A Condition step checks
@AgentStepName.RiskLevel
- Approval routes the document using context from earlier steps
- A Notify step references
@Intake.Message in the notification
- A form submission makes fields available as
@Intake.FieldName
- An Agent step uses
@Intake.CustomerName and other fields for context
- A Generate step maps
@Intake.CustomerName to template fields
- Approval routes the generated document
- A Sign step collects signatures on the generated document
Using Variables in Configuration
Variables can be referenced in:
- Agent step instructions (context)
- Generate step template mapping
- Notify step messages and conditions
- Condition step logical expressions
- Collect step recipient definition
- Approval routing and conditions
Use descriptive field names in Intake forms, document what outputs your Agent steps provide, and test variable references to make sure they’re available where you expect them.
