Azure DevOps

DevOps integration · 33 node(s).

00Overview

Wire Azure DevOps into a flow to queue pipeline runs, watch builds and pull their logs, and hand pipeline artifacts on to the rest of your automation. Manage the backlog end to end — create, update, query and comment on work items — and drive code review by opening, updating, completing and commenting on pull requests. List projects, repositories, branches, commits and teams to feed any of the above.

Every field below is exactly what you see in the Flomation editor. Fields marked ● live picker let you choose from a list pulled live from your account — no IDs to look up.

01Connecting Azure DevOps

1. In Azure DevOps, open User settings (the avatar, top-right) → Personal access tokens (dev.azure.com → User settings → Personal access tokens) and choose New Token.
2. Scope the token to what you plan to automate — Work Items (Read & write), Build (Read & execute), Code (Read & write), Project and Team (Read) and, only if you use classic releases, Release (Read, write & execute) — set an expiry, then Create. Copy the token straight away: Azure DevOps shows it once.
3. Note your Organisation URL — the modern https://dev.azure.com/your-org or the legacy https://your-org.visualstudio.com; both are accepted. Paste it into the node's Organisation URL field.
4. Leave API Version blank — it defaults to 7.1 — unless Microsoft asks you to pin a specific version.
5. In Flomation, store the token as an environment secret (e.g. azuredevops_secret) and select it in the node's Personal Access Token field.

02Branch

Azure DevOps: List Branches

devops/azuredevops/branch_get_all · Action

List a repository's branches, with each one's latest commit. Filter narrows by name prefix — "release/" returns only the release branches.

Returns: results, count, tool_result, success, error

03Build

Azure DevOps: Cancel Build

devops/azuredevops/build_cancel · Action

Cancel an in-flight build. Cancellation is a request, not an instruction: the build moves to "cancelling" and finishes tearing down, so its final result arrives shortly afterwards. This is a Build API action because the Pipelines API has no cancel verb at all.

Returns: id, result, build_status, tool_result, success, error

Azure DevOps: Get Build

devops/azuredevops/build_get · Action

Get one build by ID, including its status, result, requester and source branch.

Returns: id, result, build_status, build_result, tool_result, success, error

Azure DevOps: List Builds

devops/azuredevops/build_get_all · Action

List builds across a project, filterable by definition, status, result and branch. This is the classic Build API rather than the Pipelines API — deliberately: the Pipelines API can only list runs of ONE pipeline, so a cross-pipeline view is only available here.

Returns: results, count, tool_result, success, error

Azure DevOps: Get Build Log

devops/azuredevops/build_log_get · Action

Fetch a build's logs as text — the payload to paste into a chat message when a build fails. Leave Log ID blank to concatenate every log for the build in order; set it to fetch just one. Very large logs are truncated and flagged rather than silently clipped.

Returns: id, result, content, truncated, tool_result, success, error

04Commit

Azure DevOps: List Commits

devops/azuredevops/commit_get_all · Action

List commits in a repository, filterable by branch, author, date range and file path. Useful for building release notes or spotting what landed since a given date.

Returns: results, count, tool_result, success, error

05Pipeline

Azure DevOps: Get Pipeline Artifact

devops/azuredevops/pipeline_artifact_get · Action

Get a named artifact from a pipeline run, with a time-limited download URL. Artifacts are how a pipeline hands its output to the rest of a flow. The URL is returned rather than the bytes — build artifacts are routinely gigabytes.

Returns: id, result, download_url, expires_at, tool_result, success, error

Azure DevOps: List Pipelines

devops/azuredevops/pipeline_get_all · Action

List the pipelines in a project, returning each one's ID, name and folder. The IDs this returns are what Run Pipeline takes.

Returns: results, count, tool_result, success, error

Azure DevOps: Run Pipeline

devops/azuredevops/pipeline_run · Action

Queue a pipeline run — the headline action, and the reason to wire Azure DevOps into a flow at all. Returns immediately with the run in progress; pair it with Get Pipeline Run to wait for the outcome. Variables can be given as plain name/value pairs.

Returns: id, result, run_state, run_url, tool_result, success, error

Azure DevOps: Get Pipeline Run

devops/azuredevops/pipeline_run_get · Action

Get a pipeline run's state and result — the polling half of run, wait, report. State and Result are SEPARATE: a run is only finished when State is "completed", and until then Result reads "unknown", which does not mean it failed.

Returns: id, result, run_state, run_result, finished, tool_result, success, error

Azure DevOps: List Pipeline Runs

devops/azuredevops/pipeline_run_get_all · Action

List the recent runs of one pipeline, newest first — for "did today's build pass?" style flows. The service returns its own recent window and takes no paging parameters, so Limit trims the list on our side.

Returns: results, count, tool_result, success, error

06Pr

Azure DevOps: Comment on Pull Request

devops/azuredevops/pr_comment_add · Action

Comment on a pull request. Azure DevOps models PR comments as threads, so a new comment starts a thread; give a Thread ID to reply inside an existing one instead.

Returns: id, result, tool_result, success, error

Azure DevOps: Complete Pull Request

devops/azuredevops/pr_complete · Action

Complete (merge) a pull request, with the usual options — squash, delete the source branch, resolve linked work items. Azure DevOps refuses to merge a PR that has moved since you last read it, so this action re-reads the PR first and echoes its latest commit back; no extra step needed.

Returns: id, result, pr_status, merge_status, tool_result, success, error

Azure DevOps: Create Pull Request

devops/azuredevops/pr_create · Action

Open a pull request. Branch names can be given plainly ("main") — the full ref Azure DevOps insists on is filled in for you. Reviewers are given as identity IDs; Work Item IDs link the PR to the work it delivers.

Returns: id, result, url, tool_result, success, error

Azure DevOps: Get Pull Request

devops/azuredevops/pr_get · Action

Get one pull request, including its merge status, reviewers and the last source commit. Merge Status is what tells you whether it can actually be completed.

Returns: id, result, pr_status, merge_status, tool_result, success, error

Azure DevOps: List Pull Requests

devops/azuredevops/pr_get_all · Action

List pull requests in a repository, filterable by status, creator, reviewer and target branch. "PRs awaiting review" is the classic use — set Status to Active and give a Reviewer ID.

Returns: results, count, tool_result, success, error

Azure DevOps: Update Pull Request

devops/azuredevops/pr_update · Action

Update a pull request's title, description or target branch — and this is also how you abandon one (set Status to Abandoned) or bring it back (Active). Publishing a draft is Draft = off. To merge, use Complete Pull Request.

Returns: id, result, pr_status, tool_result, success, error

07Project

Azure DevOps: Get Project

devops/azuredevops/project_get · Action

Get one Azure DevOps project by name or ID, including its description, visibility and state. Turn on Include Capabilities to also return the process template and version-control type.

Returns: id, result, tool_result, success, error

Azure DevOps: List Projects

devops/azuredevops/project_get_all · Action

List the projects in an Azure DevOps organisation. Every other action needs a project, so this is the natural first step — and the connection test: it validates the Organisation URL and the Personal Access Token without touching anything else.

Returns: results, count, tool_result, success, error

08Release

Azure DevOps: Create Release

devops/azuredevops/release_create · Action

Create a classic release from a release pipeline. Note this is classic Release Management, which Microsoft has steered new work away from in favour of multi-stage YAML pipelines — if your project deploys from a pipeline, use Run Pipeline instead.

Returns: id, result, url, tool_result, success, error

Azure DevOps: List Releases

devops/azuredevops/release_get_all · Action

List classic releases in a project. Note this is classic Release Management, which Microsoft has steered new work away from in favour of multi-stage YAML pipelines — if your project deploys from a pipeline, use List Pipeline Runs instead.

Returns: results, count, tool_result, success, error

09Repo

Azure DevOps: Get Repository

devops/azuredevops/repo_get · Action

Get one Git repository by name or ID — its default branch, size, web URL and clone URLs.

Returns: id, result, tool_result, success, error

Azure DevOps: List Repositories

devops/azuredevops/repo_get_all · Action

List the Git repositories in a project, with each one's ID, default branch and clone URLs.

Returns: results, count, tool_result, success, error

10Team

Azure DevOps: List Teams

devops/azuredevops/team_get_all · Action

List the teams in a project. Mostly useful for scoping a WIQL query to one team's backlog, or for resolving a team ID to feed another tool.

Returns: results, count, tool_result, success, error

11Workitem

Azure DevOps: Add Work Item Comment

devops/azuredevops/workitem_comment_add · Action

Add a comment to a work item. Unlike creating or updating one, a comment is plain text on its own endpoint — no field map involved. Comments accept simple HTML for formatting.

Returns: id, result, tool_result, success, error

Azure DevOps: List Work Item Comments

devops/azuredevops/workitem_comment_get_all · Action

List the comments on a work item, newest last. Note these are the discussion comments, not the field-change history.

Returns: results, count, tool_result, success, error

Azure DevOps: Create Work Item

devops/azuredevops/workitem_create · Action

Create a work item (Bug, Task, User Story, …). Fields are given as an ordinary name/value map — "title", "assigned to", "priority" and the like, or full reference names such as System.AreaPath. The JSON-Patch document Azure DevOps actually requires is built for you.

Returns: id, result, url, tool_result, success, error

Azure DevOps: Delete Work Item

devops/azuredevops/workitem_delete · Action

Delete a work item. By default it goes to the project's recycle bin and can be restored; turn on Destroy Permanently to erase it outright, which cannot be undone.

Returns: id, result, tool_result, success, error

Azure DevOps: Get Work Item

devops/azuredevops/workitem_get · Action

Get a work item by ID. Expand pulls in relations, links or every field; Fields narrows the response to the reference names you list. The two cannot be combined — Azure DevOps rejects that pairing.

Returns: id, result, url, tool_result, success, error

Azure DevOps: Get Work Items (Batch)

devops/azuredevops/workitem_get_batch · Action

Fetch many work items by ID in one go — paste a list of IDs and get the full items back. Azure DevOps caps a batch at 200, so longer lists are split automatically. Fields and Expand cannot be combined.

Returns: results, count, tool_result, success, error

Azure DevOps: Query Work Items (WIQL)

devops/azuredevops/workitem_query_wiql · Action

Run a WIQL query and return the matching work items, fully populated. WIQL itself returns ONLY id references no matter what the SELECT clause lists, so this action hydrates them for you (in batches of 200) — otherwise the results would be unusable in a flow. Cap your query with a WHERE clause: large result sets are expensive and are trimmed at 2000 items.

Returns: results, count, tool_result, success, error

Azure DevOps: List Work Item Types

devops/azuredevops/workitem_type_get_all · Action

List the work item types available in a project — Bug, Task, User Story and whatever else the project's process template defines. Worth checking before Create Work Item: process templates are customisable, so the familiar names are not guaranteed.

Returns: results, count, tool_result, success, error

Azure DevOps: Update Work Item

devops/azuredevops/workitem_update · Action

Update a work item's fields. Give an ordinary name/value map — "state", "assigned to", "priority", or full reference names; set a value to null to clear that field. The JSON-Patch document Azure DevOps requires is built for you.

Returns: id, result, url, tool_result, success, error

12Notes & Limitations

Behaviours and constraints worth knowing before you build with these nodes.

• Run Pipeline returns the moment a run is queued rather than when it finishes, so pair it with Get Pipeline Run and poll until State reads completed before treating the result as final; until then Result reads unknown, which does not mean it failed.
• WIQL queries are trimmed at 2000 hydrated work items and are rejected outright by the service beyond roughly 20,000 matches, so constrain large queries with a WHERE clause.
• Return All stops at an internal 50-page safety cap on very large organisations and flags when it has done so, so narrow the filter rather than treat a capped list as complete.
• Work item types are defined by each project's process template, so the familiar names (Bug, Task, User Story) are not guaranteed — check List Work Item Types before Create Work Item.
• An expired or under-scoped Personal Access Token surfaces as a returned sign-in page rather than an outright rejection, so re-check the token's scopes and expiry date when calls that previously worked begin failing.
• Create Release and List Releases target classic Release Management, which Microsoft has steered new work away from — use Run Pipeline and List Pipeline Runs for projects that deploy from YAML pipelines.