ActionAzure DevOpsUpdated September 2026

How do I query Azure DevOps work items?

Short answer: You can query work items (wiql) in Azure DevOps by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Azure DevOps Query Work Items (WIQL) action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

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

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.

Triggered by

Apps that pair well as the trigger for Query Work Items (WIQL).

Any of these apps can fire this action as part of a workflow.

Google Sheets → Azure DevOps

2 Google Sheets triggers

HubSpot → Azure DevOps

18 HubSpot triggers

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 run history shows the failed step with its input and the error message Azure DevOps returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Query Work Items (WIQL) support batch operations?

Run Query Work Items (WIQL) inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Azure DevOps's rate limits.

More actions