Azure DevOps
Read and write Azure DevOps work items (WIQL), comments, areas, iterations, repositories, pull requests, threads and builds.
Keep Azure Boards, Repos and Pipelines aligned with service management, finance and portfolio systems.
Source actions
14
Destination actions
7
Data types
11
Validation status
Implemented · fixture tested.
Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.
What you can map
areas
- List area pathsSource
Area path tree of a project, flattened.
build definitions
- List pipeline definitionsSource
Build and YAML pipeline definitions in a project.
builds
- Queue buildDestinationNot retried automatically
Queues a run of a pipeline definition for a branch or commit.
- List buildsSourceIncremental
Pipeline runs (builds) in a project, oldest queued first for incremental sync.
iterations
- List iterationsSource
Iteration (sprint) tree of a project with start and finish dates, flattened.
projects
- List projectsSource
Projects in the organisation visible to the token.
pull request threads
- Add pull request commentDestinationNot retried automatically
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.
pull requests
- Create pull requestDestinationNot retried automatically
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 requestDestinationDuplicate protected
Updates title, description, draft state or target branch, or abandons and reactivates. Does not complete.
repositories
- List Git repositoriesSource
Git repositories in a project.
teams
- List teamsSource
Teams in a project.
work item comments
- Add work item commentDestinationNot retried automatically
Adds a discussion comment to a work item.
- List work item commentsSource
Discussion comments on a work item.
work items
- Create work itemDestinationNot retried automatically
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 itemDestinationDuplicate protected
Updates fields, state, tags or parent; optionally guarded by the expected revision.
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.
Provider events
Service hooks for work item, pull request, build and release events. Nexra event triggers are not yet available; flows run on demand or on a schedule.
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 and release pipelines are not implemented.
- 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 and build creates have no idempotency key; uncertain writes are not repeated automatically.