- Integrations
- /
- Azure DevOps
- /
- Actions
- /
- Query Work Items (WIQL)
ActionAzure DevOpsUpdated May 2026
How do I query Azure DevOps work items?
Short answer: Drop the "Azure DevOps → Query Work Items (WIQL)" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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.
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. Tiny Command handles Azure DevOps's rate limits automatically so you don't have to throttle manually.
More actions
Other Azure DevOps actions.
Action
Add Comment to Work Item
Posts a comment to a work item's discussion thread. Useful for "AI-summarised context → log on the work item" or for cross-tool notifications ("CI build failed → comment on the related work item with the error log").
ActionCreate Work Item
Creates a Bug, Task, User Story, Feature, or Epic with title, description, assignee, area path, plus custom fields configured per the project's process template. Required fields depend on the work-item type and project template.
ActionGet Work Item
Returns a work item by ID with all standard and custom fields, relations (parent/child links), and history if requested. The standard lookup for workflows that received a work-item ID upstream and need richer detail.
ActionUpdate Work Item
Partial update on a work item — change state, assignee, priority, or any field. For "auto-transition to Resolved when the related PR merges" or "reassign all open bugs from this engineer to their replacement" bulk-update workflows.
Send query work items (wiql) from your workflows.
Triggered by anything in the catalog. Free tier available. No credit card.