---
title: "Connect Azure DevOps and GitHub - APIANT.ai"
description: "When \"Completed Build\" fires in Azure DevOps, your agent runs \"Add Labels to Issue\" in GitHub."
canonical: "https://apiant.ai/connect/azure-devops-to-github"
---

# Connect Azure DevOps and GitHub

When **Completed Build** fires in [Azure DevOps](https://apiant.ai/connections/azure-devops), your agent runs **Add Labels to Issue** in [GitHub](https://apiant.ai/connections/github), or **New Branch** in GitHub to **Add Link to Work Item** in Azure DevOps. Describe the whole flow and it is built, tested on every scenario and kept running.

Azure DevOps **5** triggers Azure DevOps **5** actions GitHub **15** triggers GitHub **19** actions

What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.

## What do you want Azure DevOps and GitHub to do together?

Give your AI client this address.

`https://mcp.apiant.ai`

One connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.

### Set it up in your client

### Claude Code

Run this in the directory you want to work in.

`claude mcp add --transport http -s project apiant-ai https://mcp.apiant.ai`

Start Claude Code there, approve the server, and sign in in the browser page it opens.

[Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code)

### Claude, web and desktop

Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Cursor

Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Zed

Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Codex and the ChatGPT desktop app

Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Any other MCP client

Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

Example flows

## What Azure DevOps and GitHub can do together

### From Azure DevOps to GitHub

- When **Completed Build** in Azure DevOps then **Add Labels to Issue** in GitHub
- When **New Work Item** in Azure DevOps then **Create Issue** in GitHub

### From GitHub to Azure DevOps

- When **New Branch** in GitHub then **Add Link to Work Item** in Azure DevOps
- When **New Collaborator** in GitHub then **Create Work Item** in Azure DevOps

Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.

Everything your agent can do with Azure DevOps and GitHub

## Triggers and actions 20 triggers · 24 actions

- Trigger

**Code Push (Git)**

Triggers when commits are pushed to a Git repository in an Azure DevOps project.

- Trigger

**Completed Build**

Triggers when a build finishes in an Azure DevOps project, with its result (succeeded, failed, partially succeeded or canceled).

- Trigger

**New Work Item**

Triggers when a work item is created in an Azure DevOps project.

- Trigger

**New Work Item Comment**

Triggers when someone comments on a work item in an Azure DevOps project.

- Trigger

**Updated Work Item**

Triggers when a work item is updated in an Azure DevOps project, with the work item's current values and the list of fields that changed.

- Action

**Add Link to Work Item**

Adds a link to an Azure DevOps work item: a related, parent, child, predecessor, successor or duplicate link to another work item, or a hyperlink to a web page.

- Action

**Create Work Item**

Creates a new work item (such as a Task, Bug, Issue or User Story) in an Azure DevOps project.

- Action

**Find Work Item**

Finds work items in an Azure DevOps project that match a Work Item Query Language (WIQL) query, returning the matching work item IDs, or the matching links for a link query.

- Action

**Trigger Build**

Queues a new run of an Azure DevOps build pipeline, optionally for a specific branch or commit and with pipeline variables or parameters.

- Action

**Update Work Item**

Updates an existing Azure DevOps work item: changes its title, description, state, assignee, area, iteration, priority or tags, and can add a discussion comment. Fields left blank are not changed.

- Trigger

**Issue Closed**

Triggers when an issue in a repository is closed.

- Trigger

**New Branch**

Triggers when a new branch is created in a GitHub repository.

- Trigger

**New Collaborator**

Triggers when a new collaborator is added to a GitHub repository.

- Trigger

**New Commit**

Triggers when a new commit is pushed to a GitHub repository's default branch.

- Trigger

**New Commit Comment**

Triggers when someone comments on a commit in a repository.

- Trigger

**New Gist**

Triggers when you create a new gist on GitHub.

- Trigger

**New Global Event**

Triggers when a new public event happens anywhere on GitHub, such as a push, fork, or new issue.

- Trigger

**New Issue**

Triggers when a new issue is created in a repository.

- Trigger

**New Label**

Triggers when a new label is added to a GitHub repository.

- Trigger

**New Milestone**

Triggers when a new milestone is created in a repository.

- Trigger

**New Pull Request**

Triggers when a new pull request is opened in a repository.

- Trigger

**New Release**

Triggers when a new release is published in a GitHub repository.

- Trigger

**New Repo Event**

Triggers when new activity (pushes, issues, pull requests, releases and more) happens in a GitHub repository.

- Trigger

**New Repository**

Triggers when a new public repository appears under a GitHub user or organization.

- Trigger

**New Watcher**

Triggers when someone starts watching a repository.

- Action

**Add Labels to Issue**

Adds labels to an issue or pull request in a GitHub repository, keeping its existing labels.

- Action

**Check Organization Membership**

Checks whether a GitHub user is a member of an organization and returns true or false.

- Action

**Create Branch**

Creates a new branch in a repository, starting from the commit you choose.

- Action

**Create Comment**

Adds a comment to an issue or pull request in a GitHub repository.

- Action

**Create Gist**

Creates a new gist with one file on the connected GitHub account.

- Action

**Create Issue**

Creates a new issue in a GitHub repository.

- Action

**Create or Update File**

Creates a new file in a repository, or replaces an existing file's contents, as a commit.

- Action

**Create Pull Request**

Opens a pull request asking to merge one branch into another.

- Action

**Delete Branch**

Deletes a branch from a repository. Any open pull request from that branch is closed.

- Action

**Find Branch**

Finds a branch in a GitHub repository by name and returns its latest commit and protection status.

- Action

**Find Issue**

Finds an issue in a GitHub repository by its number and returns its title, body, state, author and labels.

- Action

**Find Organization**

Finds a GitHub organization by its login and returns its profile details.

- Action

**Find Pull Request**

Finds a pull request in a GitHub repository by its number and returns its title, state, branches and merge status.

- Action

**Find Repository**

Returns a GitHub repository by its owner and name, including its description, visibility, default branch and counts.

- Action

**Find User**

Finds a GitHub user by username and returns their public profile.

- Action

**Get File Contents**

Returns a file from a GitHub repository, with its base64-encoded content, at the default branch or a chosen branch, tag or commit.

- Action

**Submit Review**

Submits a review on a pull request: approve it, request changes, or leave a review comment.

- Action

**Update Issue**

Updates an existing issue in a GitHub repository, such as its title, text, state, labels or assignees.

- Action

**Update Pull Request**

Changes a pull request's title, description, target branch, or open/closed state.

## Each app on its own

- [ **Azure DevOps** Azure DevOps is where teams manage, develop, and deliver software in the cloud.](https://apiant.ai/connections/azure-devops)
- [ **GitHub** GitHub is the perfect place to share code and work collaboratively on private and open source software.](https://apiant.ai/connections/github)

Reviews

## What our customers say

## More from Azure DevOps

- [ **Azure DevOps to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/azure-devops-to-hubspot)
- [ **Azure DevOps to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/azure-devops-to-salesforce)
- [ **Azure DevOps to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/azure-devops-to-slack)
- [ **Azure DevOps to Google Sheets** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/azure-devops-to-google-sheets)
- [ **Azure DevOps to Gmail** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/azure-devops-to-gmail)
- [ **Azure DevOps to Google Calendar** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/azure-devops-to-google-calendar)

## More into GitHub

- [ **ActiveCampaign to GitHub** ActiveCampaign is a marketing automation, email marketing, and CRM platform.](https://apiant.ai/connect/activecampaign-to-github)
- [ **Airtable to GitHub** Organize anything with Airtable, a modern database created for everyone.](https://apiant.ai/connect/airtable-to-github)
- [ **Asana to GitHub** Asana is a collaborative information manager for workspace.](https://apiant.ai/connect/asana-to-github)
- [ **ClickUp to GitHub** ClickUp is an all-in-one app to plan, track, and manage your work in a beautifully intuitive environment.](https://apiant.ai/connect/clickup-to-github)
- [ **Discord to GitHub** Discord is an all-in-one voice and text chat for gamers.](https://apiant.ai/connect/discord-to-github)
- [ **Freshdesk to GitHub** Freshdesk is a cloud-based customer support and helpdesk platform.](https://apiant.ai/connect/freshdesk-to-github)

Questions

## Azure DevOps and GitHub, answered

###

### What can start an automation from Azure DevOps?

Any of Azure DevOps's 5 triggers in the catalog, including Completed Build, New Work Item, New Work Item Comment and Updated Work Item. Describe the moment in plain language and your agent picks the right one.

###

### What can your agent do in GitHub when something happens in Azure DevOps?

Any of GitHub's 19 actions, including Create Branch, Create Comment, Create Gist and Create Issue. Your agent maps the data both ways and tests every scenario before it ships.

###

### Can it also run from GitHub to Azure DevOps?

Yes. When something happens in GitHub, your agent can act in Azure DevOps too. This page covers both directions: GitHub's triggers and Azure DevOps's actions are listed here as well.

###

### Do I have to build a connector for Azure DevOps or GitHub?

No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.

###

### Can my AI client use Azure DevOps and GitHub without building an automation?

Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.

###

### What happens when something fails?

Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.

###

### Is there a free plan?

Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.
