ActionAzure DevOpsUpdated September 2026

How do I create a work item in Azure DevOps?

Short answer: You can create work item in Azure DevOps by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Azure DevOps Create Work Item action to a workflow, map its 6 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Create Work Item in Azure DevOps — start free All 5 Azure DevOps actions

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.

Triggered by

Apps that pair well as the trigger for Create 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 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 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 Create Work Item support batch operations?

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