Variables

Variables 101

Variables let one step use the output of another step. Use them in text fields, prompts, and configuration inputs to reference trigger inputs or outputs from previous steps.

What Are Variables

References to:

• Input variables – Data provided when the automation runs (from the trigger)
• Step outputs – Data produced by earlier steps

Variables are resolved at runtime when the step executes.

Variable Syntax

• Simple: #variableName# – References the whole output
• Field access: #StepName.fieldName# – References a specific field
• Nested: #StepName.field.nestedField# – References nested fields
• Array access: #StepName[0]# – References the first item
• Array item field: #StepName[0].fieldName# – References a field of an array item

Where to Use Them

• Text and prompt fields (Generate Text, Email body, Slack message)
• Step configuration inputs that support variables
• Filename fields, subject lines, and other string inputs
• Variable editor fields (rich text with full variable support)

Inserting Variables Safely

In most variable-enabled fields:

1. Click into the field
2. Type #
3. Pick from a menu:
   • Trigger inputs
   • Previous step outputs
   • Specific fields
4. Select to insert — avoids typos and mismatched field names

Examples

• Trigger input: #ManualTrigger.customerName# – Customer name from the manual trigger
• Previous step: #GenerateText.output# – Output from a Generate Text step
• Nested: #HubSpotContact.properties.email# – Email from a HubSpot contact
• Array: #GmailNewEmail.attachments[0].filename# – First attachment filename

Output Schema

Each step defines an output schema. View it in the step configuration dialog under Output Schema. Use those field names in your variable references.

Variable and input types

When you configure a step, many inputs accept variables. Two common input types:

Text Field

Single-line or multi-line text. You can type variables (e.g. #StepName.field#) or use the # picker to insert them. Use for prompts, message bodies, subjects, and other string inputs.

File Upload

Some steps accept a file as input (e.g. from the trigger or a previous step that outputs file data). The step configuration may show a file picker or a variable field that references an attachment or file output. Use the variable picker to bind the output of a step that provides files (e.g. trigger attachment, or “get file” from Drive/OneDrive).

Best Practices

• Prefer referencing a specific field (e.g., #Step.email#) over a whole object
• Test with real inputs; check how null/empty values behave
• Use the Output Schema in each step as your “source of truth” for field names