Skip to main content

Use Variables in Automations

Use variables to insert values from the automation trigger, earlier step outputs, and run-level values into action fields such as prompts, comments, emails, webhook bodies, and ticket IDs.

Syntax​

Wrap variable paths in double curly braces. The first part of the path is either a trigger input slug, a step slug, or a run variable.

{{slug.variable}}

Top-level run variables do not need a dot:

{{today}}
{{now}}

Step output variables use the step slug followed by the output field. The slug is shown on the step card and execution details. Each step's available inputs and outputs are documented on that step's own reference page.

{{chat1.completion}}
{{googleFile1.markdown}}
{{page1.markdown}}

A step can use variables from the trigger, run variables, and completed upstream steps. Variable paths are case-sensitive.

Run Variables​

These variables are available to every step. They use the teamspace timezone.

VariableWhat it means
{{today}}Current date, formatted as YYYY-MM-DD.
{{now}}Current date and time, formatted as YYYY-MM-DD HH:mm.
{{startOfWeek}}Monday date for the current week.
{{endOfWeek}}Sunday date for the current week.
{{startOfLastWeek}}Monday date for the previous week.
{{endOfLastWeek}}Sunday date for the previous week.
{{weekNumber}}Current ISO week number.
{{startOfMonth}}First date of the current month.
{{endOfMonth}}Last date of the current month.
{{startOfLastMonth}}First date of the previous month.
{{endOfLastMonth}}Last date of the previous month.

Use run variables when the automation should adapt to the date it runs. For example, a weekly summary prompt can ask for highlights created between {{startOfWeek}} and {{endOfWeek}}, while a monthly report can use {{startOfMonth}} and {{endOfMonth}}.

Step Variables​

Trigger variables and step output variables are documented on the individual step pages in Automation steps. Use those pages when you need to know which variables a step exposes and which configuration fields accept variables.

Common step reference pages include:

Tips​

  • Copy variable paths exactly. Variable paths are case-sensitive.
  • Keep the {{ and }} braces in place.
  • Use the slug shown on a step to reference that step's output. If you rename, reorder, or move a step, keep using the slug shown on that step.
  • A step can only reference outputs from completed upstream steps.
  • If a variable renders empty, check that the field exists on the trigger input or step output and that the step has already completed.

FAQ​

Why is my variable showing as plain text instead of a value?​

Check that the variable path is correct, the braces are still present, and the trigger or upstream step provides that value.