Workflow metadata provides information about the current execution and is automatically available in the context. You can use metadata to build more flexible workflows and include dynamic details in messages, tickets, logs, and debugging steps. Metadata can also be passed to nested workflows.

Access metadata

Use metadata: Reference metadata using {{ $.metadata.<field> }}

Common metadata fields

Field	Description
`account_id`	The ID of the workspace where the workflow is executed.
`account_name`	The name of the workspace where the workflow is executed.
`case.id`	The ID of the case from which the workflow was triggered (if applicable).
`event_id`	The ID of the trigger event.
`execution_id`	The ID of the current execution.
`execution_nested_level`	The nesting level of the execution.
`execution_url`	A link to the execution Run Log in Torq.
`parent_execution_id`	The ID of the parent execution.
`parent_workflow_id`	The ID of the parent workflow.
`user_email`	The email of the user who triggered the workflow (if applicable).
`workflow_id`	The ID of the workflow being executed.
`workflow_name`	The name of the workflow being executed.
`workflow_revision_id`	The ID of the workflow revision being executed.

Nested Workflows in Torq: Improve Modularity and Reusability

Activity Log: Monitor Workflow Executions in Torq

Workflow Template: AlienVault URL Enrichment with Cache

Workflow Template: VirusTotal URL Enrichment with Cache

Wait Operator: Precisely Pause Workflow Progress with Torq

Workflow Metadata: Enrich Executions with Additional Context

Access metadata

Common metadata fields