Azure DevOps
Azure DevOps work items and WIQL queries
Azure DevOps is Microsoft's developer-platform stack — git repos, CI/CD pipelines, work-item tracking, and test plans, all unified under an Azure AD-backed organisation. Tiny Command exposes five actions (no triggers — Azure DevOps has Service Hooks configured in the project admin UI rather than subscribed via API; point a Service Hook at a Tiny Command webhook trigger URL for event-driven workflows): Create Work Item, Update Work Item, Get Work Item, Add Comment to Work Item, and Query Work Items (WIQL — Work Item Query Language, Azure DevOps's SQL-like syntax for filtering across the entire work-item store). The connection uses a Personal Access Token (PAT) from User Settings → Personal Access Tokens, scoped to Work Items (Read & Write). Create Work Item is process-template-aware: the work-item type (Bug, Task, User Story, Feature, Epic) and the required fields depend on the project's process template (Agile, Scrum, CMMI, or Basic). The picker in Tiny Command auto-resolves the type and field schema from the connected project.
Do anything Azure DevOps can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| 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"). |
| 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. |
| Get Work Item | 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. |
| 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. |
| 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. |
Pre-built Azure DevOps workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
AI-triage every Azure DevOps event, ping the right channel only when it matters.
Every event matching a filter, appended to a running spreadsheet.
Turn Azure DevOps into a Notion-backed source of truth, auto-tagged.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect Azure DevOps once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every Azure DevOps field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the Azure DevOps integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect Azure DevOps to Tiny Command?
What Azure DevOps triggers does Tiny Command support?
What Azure DevOps actions can I run from a workflow?
Is the Azure DevOps integration real-time?
Do I need to write code to use Azure DevOps with Tiny Command?
How much does the Azure DevOps integration cost?
More developer tools apps people connect.
Same category as Azure DevOps, ordered by how often teams pair them. Hover the carousel to pause.
Do more with Azure DevOps.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
