Use variables in workflows

Use data from the current run

Variables let later steps reuse values from earlier steps or from the incoming trigger payload. This keeps workflows flexible without adding more steps.

Prefer the smallest variable that solves the problem. A single field is easier to reason about than a full payload shape.

• Use trigger data for values that arrive when the workflow starts.
• Use step output when a previous action produced the value you need.
• Use fallback text when a field might be empty.

Format the output for the next system

Build the final message, title, or command argument with the format the receiving app expects.

When a value might contain spaces or punctuation, test the rendered output before you publish the workflow.

Keep the variable path visible

Name steps so the source of each value stays obvious in the editor.

When a workflow grows, a clear variable path matters more than saving a few characters.