Environment variables (advanced)
- On this page
- Environment variables (advanced)
- The execution uuid
- The workflow uuid
- Callable workflow trigger variables
The following environment variables are available in your workflows:
1$.env.execution_uuid2$.env.execution_start_time3$.env.execution_log_url4$.env.workflow_uuid5$.env.workflow_title
Embedded users can use more environment variables not listed here. For a detailed guide please see our guide to Embedded environment variables
The execution uuidCopied!
The $.env.execution_uuid variable is potentially of key importance in managing statuses and errors. It is the id which is generated every time a workflow is run. It could be linked to an external execution id (which may have been pulled in from a webhook) - both of which could be stored in Data Storage and retrieved later in the workflow or stored at account level and retrieved in any child workflows which are called.
The workflow uuidCopied!
The $.env.workflow_uuid variable is basically the uuid found in your workflow url:
An example of using $.env.workflow_uuid can be found in our documentation on workflow threads
In this case it is used as a suffix for an account-level data storage variable, to identify that the variable is connected to that workflow.
Callable workflow trigger variablesCopied!
Callable workflows have the following variables available from their trigger output:
1$.steps.trigger.#calling_workflow2$.steps.trigger.#calling_execution3$.steps.trigger.#calling_execution_log_url
The $.steps.trigger.#calling_workflow variable can be used to obtain the uuid of the calling workflow.
Again, this is used in our documentation on workflow threads - to make sure the calling workflow accesses the account-level data storage list that was created by the calling workflow.