ActionAzure DevOpsUpdated September 2026

How do I add a comment to an Azure DevOps work item?

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

Add Comment to Work Item in Azure DevOps — start free All 5 Azure DevOps actions

Add Comment to 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
Work Item ID work_item_id	string	Required	–
Comment text	string	Required	–

Sample request

{
  "work_item_id": "{{trigger.work_item_id}}",
  "text": "{{trigger.text}}"
}

Returns

{
  "id": 100,
  "text": "Done",
  "createdDate": "2026-05-11T00:00:00Z"
}

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

Triggered by

Apps that pair well as the trigger for Add Comment to 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 Add Comment to Work Item.

What does the Add Comment to Work Item action do in Azure DevOps?

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").

What inputs does Add Comment to Work Item require?

Required: Work Item ID, Comment. 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 Add Comment to Work Item support batch operations?

Run Add Comment to 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