ActionAzure DevOpsUpdated May 2026

How do I fetch an Azure DevOps work item?

Short answer: Drop the "Azure DevOps → Get Work Item" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 5 Azure DevOps actions

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
Work Item ID id	string	Required	—

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.

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 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 Get Work Item support batch operations?

Yes. Run Get Work Item 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