Skip to main content
Utility variables provide metadata about the current Workflow execution. Use them to personalize outputs, create audit trails, send contextual notifications, and implement conditional logic based on run details.

​
Access utility variables

1

Open the variable selector

While editing an action’s prompt or input field, type # or click Insert Variable. A dropdown appears showing trigger inputs and action outputs.
Variable selector dropdown showing trigger inputs and action outputs
2

Navigate to Utilities

In the dropdown, hover over Utilities to expand the available utility variables.
Utilities section expanded in the variable selector showing Workflow Run, Run by User, and Workflow variables
3

Select a variable

Click the variable you want to insert. Cassidy formats it with the correct syntax automatically.
For general information on variables, see referencing variables.

​
Available variables

​
Workflow Run

VariableDescription
IDUnique identifier for this specific run
LinkDirect URL to view this run in Cassidy
Started At Date (UTC)The date the run began, in UTC
Started At Date & Time (UTC)Full timestamp (date and time) when the run started, in UTC
Is Test Runtrue if this is a test execution, false for live runs

​
Run by User

VariableDescription
NameFull name of the user who initiated the run
EmailEmail address of the user who triggered the run
RoleOrganizational role of the user (Member or Admin)

​
Workflow

VariableDescription
NameDisplay name of the Workflow
LinkDirect URL to the Workflow configuration page
IDUnique identifier for the Workflow itself (not the specific run)

​
Common use cases

Include the runner’s name in email outputs or customize content based on their role. For example, add "Prepared by: #Run by User > Name" to a generated report.
Include the Run ID, user email, and timestamp in output files for compliance tracking. This is especially useful when Workflows process sensitive data or interact with external systems.
Send Slack messages or emails that include who ran the Workflow, when it started, and a link to the run for quick reference.
Use Is Test Run with Paths to behave differently during testing vs live execution. For example, skip sending real emails during test runs, or write to a staging database instead of production.
Include the Workflow name and link in generated reports or communications so recipients can easily navigate back to the source automation.

​
Next steps

Reference variables

Learn how to pass data between Workflow steps using all variable types.

Structured output fields

Define consistent output formats for your Workflow actions.