How to create work item in Azure DevOps

Create 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.

Field	Type	Required	Description
Type type	options	Required	–
Title title	string	Required	–
Description description	string	Optional	–
Assigned To (email) assigned_to	string	Optional	–
Tags (semicolon-separated) tags	string	Optional	–
Priority priority	options	Optional	–

Sample request

{
  "type": "{{trigger.type}}",
  "title": "{{trigger.title}}",
  "description": "{{trigger.description}}",
  "assigned_to": "{{trigger.assigned_to}}",
  "tags": "{{trigger.tags}}"
}

Returns

{
  "id": 42,
  "rev": 1,
  "_links": {
    "html": {
      "href": "https://dev.azure.com/..."
    }
  },
  "fields": {
    "System.State": "New",
    "System.Title": "Fix login bug"
  }
}

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

FAQ

Questions about Create Work Item.

What does the Create Work Item action do in Azure DevOps?

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.

What inputs does Create Work Item require?

Required: Type, Title. 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 Create Work Item support batch operations?

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