Skip to main content
Tags are string labels stored on workflow and agent executions. Use request IDs, queue names, or batch IDs to find related runs. Tags are separate from automation inputs.

​
Studio

On Trigger, enter one execution tag per line before starting a run. On Runs, enter an exact tag in the tag filter. Clicking a tag in run details opens matching history. Connect → Start run documents the tags request field. Enter example tags to generate matching REST, TypeScript, and Python requests. Connect → List runs documents the tag filter.

​
API

The tags field accepts either one string or a string array. For multipart requests, send the field as JSON, for example -F 'tags=["request-123","batch-7"]'. Find runs with GET /api/v1/runs?tag=request-123, then retrieve their outputs using GET /api/v1/runs/{id}. List and detail responses include the stored tags array.

​
SDKs

​
CLI

The start flag applies to ad-hoc runs, including runs with uploaded files. Dataset example runs do not accept --tag.

​
Child workflows

Select Child execution in an Invoke workflow step, then enter a JSON array or one expression returning an array in Execution tags. The array length can change between runs.
Tags apply to the child execution. Inline invocations do not create a separate execution and reject tags. Children do not inherit parent tags; pass the tags explicitly. Combine two dynamic arrays in the field:
For a literal array, enter ["request-123", "batch-7"]. You can also reference an array from a previous step, such as {{ steps.extract.output.tags }}. No fixed number of tag rows is required.

​
Matching and limits

  • Matching is exact and case-sensitive. Request-123 and request-123 differ.
  • Commas and whitespace are part of the tag. Tags are never split on commas or trimmed.
  • Duplicate tags are removed. Empty or whitespace-only tags are rejected.
  • Up to 100 submitted tags, with up to 256 characters per tag.
  • Existing and untagged runs have tags: []. Retries and reruns preserve tags.
Numeric IDs resolved by templates in child invocation steps are converted to strings before validation. The REST API and SDK inputs still require string tags. Multipart requests can send a single plain tag (-F 'tags=request-123') or a JSON string array (-F 'tags=["request-123","batch-7"]').