Start free
ActionAzure DevOpsUpdated September 2026

How do I fetch an Azure DevOps work item?

Short answer: You can get work item in Azure DevOps by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Azure DevOps Get Work Item 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.

Get Work Item in Azure DevOps — start free All 5 Azure DevOps actions
Get Work Item 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.

FieldTypeRequiredDescription
Work Item ID
id
stringRequired–
Sample request
{
  "id": "{{trigger.id}}"
}
Returns
{
  "id": 42,
  "fields": {
    "System.State": "Active",
    "System.Title": "Bug",
    "System.AssignedTo": {
      "displayName": "Jane"
    }
  }
}

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

Triggered by

Apps that pair well as the trigger for Get Work Item.

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

Gmail → Azure DevOps
1 Gmail triggers
Slack → Azure DevOps
13 Slack triggers
Google Sheets → Azure DevOps
2 Google Sheets triggers
HubSpot → Azure DevOps
18 HubSpot triggers
FAQ

Questions about Get Work Item.

What does the Get Work Item action do in Azure DevOps?
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.
What inputs does Get Work Item require?
Required: Work Item ID. 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 Get Work Item support batch operations?
Run Get Work Item 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

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").
Action
Create 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.
Action
Query Work Items (WIQL)
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.
Action
Update 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.
Get Work Item in Azure DevOps — start free