Skip to content

Start building

Integration · Developer

AI agents for Azure DevOps

Create, read and query Azure Boards work items, list pull requests and start pipelines in an Azure DevOps organization, with a personal access token.

Actions
6
Read
4
Write
2

Actions

What your agents can do in Azure DevOps

6 actions. Each one is a tool your agents can call and a step your workflows can run.

Read 4

Look things up. Nothing changes.

  • List projects

    Lists the projects in the organization that the token's owner can see: each project's ID, name, description, state and visibility.

  • Get work items

    Reads up to 50 work items by their IDs, in any project: each one's id, rev and fields (System.Title, System.State, System.WorkItemType, System.AssignedTo, System.Description …).

  • Find work items with WIQL

    Runs a WIQL query in a project and returns the matching work items' IDs in workItems (then read them with get_work_items), most relevant order as the query says.

  • List pull requests

    Lists the pull requests in a Git repository, newest first: active ones unless another status is asked for, optionally only those into or from a branch.

Write 2

Create, change or send.

  • Create a work item

    Creates a work item in a project: a Bug, Task, User Story, Product Backlog Item, Issue or any type the project's process has, by its name.

  • Run a pipeline

    Starts a run of a YAML pipeline, by its numeric ID (in its web address, definitionId=), on a branch (the pipeline's default branch if none), with optional runtime parameters and variables.

A person can approve first

Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything.

Connection

How it connects

Connect it once in the console, then give it to the agents and workflows that need it.

Username and key

Enter the API credentials from your Azure DevOps account.

What you enter

  • Personal access token

Settings

  • Organization

Kept safe

  • Credentials are stored encrypted with your organization's own keys.
  • They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
  • Calls go only to the tool's own servers.

How we protect your data

Ideas

Ideas to start with

Starting points made only from the actions above. Mix them with any other tool your agents can use.

  • 01

    Ask about your Azure DevOps data

    Ask a question in plain words. The agent can list projects, get work items or find work items with WIQL in Azure DevOps, then answers with what it found.

  • 02

    Let an agent update Azure DevOps

    Have the agent create a work item or run a pipeline in Azure DevOps as part of a larger task. Turn on approval and a person signs off on each change first.

  • 03

    Share what it finds in Slack

    Give one agent Azure DevOps and Slack: it can list projects in Azure DevOps and post a summary to a Slack channel in the same run.

FAQ

Azure DevOps and MyDeepAgents

Can MyDeepAgents connect to Azure DevOps?

Yes. The Azure DevOps connector has 6 actions: 4 read and 2 make changes. Your agents can call them as tools, and your workflows can run them as steps.

How do I connect Azure DevOps?

Enter the API credentials from your Azure DevOps account. You'll need: Personal access token. The connection also asks for: Organization. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.

Can an agent change data in Azure DevOps without asking?

Only if you let it. Each of the 2 actions that change data can be set to wait for a person's approval before it runs.

Can I use Azure DevOps in workflows as well as agents?

Yes. Every Azure DevOps action also works as a step in a workflow, and the same connection serves your agents and your workflows.

Early access

Put Azure DevOps to work

Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.