How to query work items (wiql) in Azure DevOps

Query Work Items (WIQL) in Azure DevOps — start free

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
WIQL Query query	string	Required	SELECT [System.Id], [System.Title] FROM WorkItems WHERE [System.State] = 'Active'

Sample request

{
  "query": "SELECT [System.Id], [System.Title] FROM WorkItems WHERE [System.State] = 'Active'"
}

Returns

{
  "workItems": [
    {
      "id": 42,
      "url": "https://dev.azure.com/..."
    }
  ]
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Query Work Items (WIQL).

What does the Query Work Items (WIQL) action do in Azure DevOps?

Runs a Work Item Query Language (WIQL) statement — Azure DevOps's SQL-like syntax for filtering across the work-item store. Returns matching work-item IDs; follow up with Get Work Item for full payload. Useful for dashboards and reporting workflows.

What inputs does Query Work Items (WIQL) require?

Required: WIQL Query. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Azure DevOps returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Query Work Items (WIQL) support batch operations?

Yes. Run Query Work Items (WIQL) inside a Loop node to process arrays. TinyCommand handles Azure DevOps's rate limits automatically so you don't have to throttle manually.

More actions