---
title: "Connect Azure DevOps and Halo Service Solutions - APIANT.ai"
description: "When \"Completed Build\" fires in Azure DevOps, your agent runs \"Add action to ticket\" in Halo Service Solutions."
canonical: "https://apiant.ai/connect/azure-devops-to-halo-service-solutions"
---

# Connect Azure DevOps and Halo Service Solutions

When **Completed Build** fires in [Azure DevOps](https://apiant.ai/connections/azure-devops), your agent runs **Add action to ticket** in [Halo Service Solutions](https://apiant.ai/connections/halo-service-solutions), or **New Ticket** in Halo Service Solutions 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 Halo Service Solutions **2** triggers Halo Service Solutions **14** 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 Halo Service Solutions 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 Halo Service Solutions can do together

### From Azure DevOps to Halo Service Solutions

- When **Completed Build** in Azure DevOps then **Add action to ticket** in Halo Service Solutions
- When **New Work Item** in Azure DevOps then **Create Ticket** in Halo Service Solutions

### From Halo Service Solutions to Azure DevOps

- When **New Ticket** in Halo Service Solutions then **Add Link to Work Item** in Azure DevOps
- When **Ticket Updated** in Halo Service Solutions 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 Halo Service Solutions

## Triggers and actions 7 triggers · 19 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

**New Ticket**

Triggers when a new ticket is logged in Halo.

- Trigger

**Ticket Updated**

Triggers when a ticket is created or updated in Halo.

- Action

**Add action to ticket**

Adds a new action (note, update or outcome) to an existing Halo ticket.

- Action

**Add project**

Creates a new project in Halo and returns the created project record.

- Action

**Create Site**

Creates a new site for a customer in Halo.

- Action

**Create Ticket**

Creates a new ticket in Halo with a summary, description and optional customer, user, type, priority, status and assignment.

- Action

**Create User**

Creates a new end user in Halo under the chosen site.

- Action

**Get customer**

Returns a single Halo customer (client) by its ID, optionally with extra details and ticket activity.

- Action

**Get project**

Returns a single Halo project by its ID, including its details and custom fields.

- Action

**Get ticket**

Returns a single Halo ticket by its ID, optionally with extra details and its last action.

- Action

**Get user**

Returns a single Halo user (end-user contact) by ID, with optional details, ticket activity and pop-ups.

- Action

**List customers**

Returns a list of customers (clients) in Halo, optionally filtered by search text or top level.

- Action

**List tickets**

Returns tickets from Halo, optionally filtered by customer, agent, status, dates, search text and more.

- Action

**List users**

Returns the users (end-user contacts) in Halo, optionally filtered by customer, site, search text and other criteria.

- Action

**Update ticket**

Updates an existing Halo ticket's summary, details, customer, assignment, status, priority and category. Fields left blank are not changed.

- Action

**Update user**

Updates an existing Halo user's name, site, email or phone number. Fields left blank keep their current values.

## 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)
- [ **Halo Service Solutions** Halo Service Solutions is a UK based company, which provides Service Desk, ITSM and PSA software solutions.](https://apiant.ai/connections/halo-service-solutions)

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 Halo Service Solutions

- [ **Google Sheets to Halo Service Solutions** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-halo-service-solutions)
- [ **Gmail to Halo Service Solutions** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-halo-service-solutions)
- [ **Google Calendar to Halo Service Solutions** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-halo-service-solutions)
- [ **Google Drive to Halo Service Solutions** Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...](https://apiant.ai/connect/google-drive-to-halo-service-solutions)
- [ **ActiveCampaign to Halo Service Solutions** ActiveCampaign is a marketing automation, email marketing, and CRM platform.](https://apiant.ai/connect/activecampaign-to-halo-service-solutions)
- [ **Airtable to Halo Service Solutions** Organize anything with Airtable, a modern database created for everyone.](https://apiant.ai/connect/airtable-to-halo-service-solutions)

Questions

## Azure DevOps and Halo Service Solutions, 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 Halo Service Solutions when something happens in Azure DevOps?

Any of Halo Service Solutions's 14 actions, including Create Site, Create Ticket, Create User and Update ticket. Your agent maps the data both ways and tests every scenario before it ships.

###

### Can it also run from Halo Service Solutions to Azure DevOps?

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

###

### Do I have to build a connector for Azure DevOps or Halo Service Solutions?

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 Halo Service Solutions 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.
