Azure DevOps
Turn incidents and requests into Azure DevOps work items, and keep status in step across your tools.
31 ways to read, 12 ways to write, each write switched on by you.
Quality checks
Built and tested with example responses.
- Ready to connect: doneEvery listed action is built in.
- Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Connected, approved, proven.
The things teams do most with Azure DevOps, an example flow with a person in the loop, and what Nexra keeps as proof.
Top actions
- Create area pathApproval by rule
- Queue buildApproval by rule
- List area pathsRead
Example flow
- Azure DevOps · List area pathsDone
- Azure DevOps · Create area pathNeeds approval
- Nexra · Record the decision and result in the evidence chainProven
Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Azure DevOps.
What gets logged
- Whether it ran on its own or who approved it, and under which rule
- A fingerprint of the exact request sent to Azure DevOps
- Azure DevOps's reply: what it created or changed
- One entry in the evidence chain, linked to the one before
Try this in the sandbox
Run the whole flow with test data in your sandbox, then connect a Microsoft test account before you go live.
For developers
Technical detail
Read and write Azure DevOps work items, comments, areas, iterations, teams, repositories, commits, pull requests, threads, builds, pipeline runs, releases and users.
Microsoft API docs- Source actions
- 31
- Destination actions
- 12
- Data types
- 25
What you can map
Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.
Areas2
- Create area pathDestinationProvider duplicate protectionApproval before production
Adds an area path under the project root or a parent area.
- List area pathsSource
Area path tree of a project, flattened.
Branches1
- List branchesSource
Branches of a repository with their head commit and lock state.
Build definitions1
- List pipeline definitionsSource
Build and YAML pipeline definitions in a project.
Builds3
- Queue buildDestinationNot retried automaticallyApproval before production
Queues a run of a pipeline definition for a branch or commit.
- Get buildSource
One pipeline run (build) with status, result, branch and requester.
- List buildsSourceIncremental
Pipeline runs (builds) in a project, oldest queued first for incremental sync.
Code1
- Search codeSource
Files in a project's repositories that match a code search, with repository and branch.
Commits2
- Get commitSource
One commit with author, committer, parents and change counts.
- List commitsSourceIncremental
Commits in a repository, optionally on one branch, by author or in a date range, newest first.
Iterations2
- Create iterationDestinationProvider duplicate protectionApproval before production
Adds an iteration (sprint) with optional start and finish dates.
- List iterationsSource
Iteration (sprint) tree of a project with start and finish dates, flattened.
Pipeline runs1
- List pipeline runsSource
Recent runs of a YAML pipeline with state and result.
Projects2
- Get projectSource
One project with its process template, source control type and default team.
- List projectsSource
Projects in the organisation visible to the token.
Pull request comments1
- Reply in pull request threadDestinationNot retried automaticallyApproval before production
Adds a comment to an existing pull request thread.
Pull request threads3
- Add pull request commentDestinationNot retried automaticallyApproval before production
Starts a comment thread on a pull request, optionally on a file.
- List pull request threadsSource
Comment threads on a pull request with their comments and status.
- Update pull request thread statusDestinationProvider duplicate protectionApproval before production
Resolves, closes or reactivates a pull request comment thread.
Pull request work items1
- List pull request work itemsSource
Work items linked to a pull request.
Pull requests4
- Create pull requestDestinationNot retried automaticallyApproval before production
Opens a pull request between two branches, optionally as a draft with reviewers.
- Get pull requestSource
One pull request with reviewers, votes and merge status.
- List pull requestsSourceIncremental
Pull requests in a project, optionally for one repository, newest first.
- Update pull requestDestinationProvider duplicate protectionApproval before production
Updates title, description, draft state or target branch, or abandons and reactivates. Does not complete.
Pushes1
- List pushesSourceIncremental
Pushes to a repository with the pusher and updated branches, newest first.
Releases1
- List releasesSourceIncremental
Classic releases in a project with definition, status and environments, oldest first.
Repositories2
- Get Git repositorySource
One repository with its default branch and project.
- List Git repositoriesSource
Git repositories in a project.
Team iterations1
- List team sprintsSource
Iterations a team has selected, with dates and past, current or future timeframe.
Team members1
- List team membersSource
Members of a team with their team administrator flag.
Teams1
- List teamsSource
Teams in a project.
Users1
- List usersSource
Users in the organisation from the Graph API, with sign-in name and origin.
Work item comments3
- Add work item commentDestinationNot retried automaticallyApproval before production
Adds a discussion comment to a work item.
- List work item commentsSource
Discussion comments on a work item.
- Update work item commentDestinationProvider duplicate protectionApproval before production
Replaces the text of a work item discussion comment.
Work item fields1
- List work item fieldsSource
Field definitions with reference name, type and picklist, including Custom.* fields.
Work item types1
- List work item typesSource
Work item types in a project with their states and state categories.
Work item updates1
- List work item historySource
Revisions of a work item with the old and new value of every changed field.
Work items5
- Create work itemDestinationNot retried automaticallyApproval before production
Creates a work item of any type with standard, scheduling and custom fields and an optional parent.
- Get work itemSource
One work item with all fields and relations.
- Get work items by IDSource
Fields and relations for up to 200 work items, for example IDs from Find work items.
- Find work items (WIQL)SourceIncremental
Work item IDs in a project matching type, state, area, iteration and changed-since filters, in ID order.
- Update work itemDestinationProvider duplicate protectionApproval before production
Updates fields, state, tags or parent; optionally guarded by the expected revision.
Access and limits
- Authentication
- Personal access token
- Plans and access
- Azure DevOps Services organisations (Basic access for Boards and Repos writes; Stakeholders have limited work item rights). Results follow the PAT owner's permissions and the scopes chosen when the token was created. Organisations can restrict or disable PAT creation.
- Test environment
- A free Azure DevOps organisation (up to five Basic users) works for testing.
- Rate limits
- Resource-based throttling in TSTUs per user over a sliding five-minute window; delayed or rejected requests return HTTP 429 with Retry-After.
- Pagination
- WIQL keyset paging on work item ID; continuation tokens (x-ms-continuationtoken header or body) for builds, definitions, refs, users, releases and comments; $top/$skip for projects, teams, members, pull requests, commits, pushes, work item updates and code search.
- Provider events
- Service hooks for work item, pull request, build and release events. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.
Before you build a flow
- Work item search returns IDs from WIQL; fetch fields with work_items.list (batch of up to 200 IDs). Nexra makes one provider call per operation, so the two steps are separate operations.
- Work item comments use the preview API version 7.1-preview.4, the only version Microsoft publishes for comments.
- Completing (merging) pull requests, deleting work items, comments, nodes or branches, cancelling builds, and creating or deploying releases are intentionally not implemented.
- Releases are read-only and come from the classic Release Management API (vsrm.dev.azure.com); YAML pipeline runs are read with pipeline_runs.list.
- Code search (almsearch.dev.azure.com) needs the Code Search extension, which is installed by default on Azure DevOps Services; results return file locations, not file content.
- Pipeline runs list the most recent runs of one pipeline; Microsoft documents no paging or time filter for this endpoint.
- Team iterations return the sprints a team has selected; pass the timeframe input to return only the current sprint.
- Azure DevOps Server (on-premises) and Microsoft Entra OAuth are not supported; use Azure DevOps Services with a PAT.
- Work item, comment, pull request, thread, thread reply and build creates have no idempotency key; uncertain writes are not repeated automatically. Area and iteration creates converge because Azure DevOps rejects a duplicate name under the same parent.
Developer reference
- Create the Microsoft credentials described above with the narrowest permissions your flows need.
- In Nexra, open Connect, then Connections, then New connection, choose Azure DevOps, enter its settings and credentials, and tick only the write actions you need. Connection guide
- Test the connection, then use its actions as flow sources and destinations. Flow guide
Machine-readable detail: GET /api/public/connect/connectors/azure-devops and the Connections API.