---
title: "Connect Azure DevOps to Pylon - APIANT.ai"
description: "When \"Completed Build\" fires in Azure DevOps, your agent runs \"Add internal note to issue\" in Pylon."
canonical: "https://apiant.ai/connect/azure-devops-to-pylon"
---

# Connect Azure DevOps to Pylon

When **Completed Build** fires in [Azure DevOps](https://apiant.ai/connections/azure-devops), your agent runs **Add internal note to issue** in [Pylon](https://apiant.ai/connections/pylon). Describe the whole flow and it is built, tested on every scenario and kept running.

Azure DevOps **5** triggers Azure DevOps **5** actions Pylon **25** 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 Pylon 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 can start in Pylon

- When **Completed Build** in Azure DevOps then **Add internal note to issue** in Pylon
- When **New Work Item** in Azure DevOps then **Add task** in Pylon

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 Pylon

## Triggers and actions 5 triggers · 30 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.

- Action

**Add internal note to issue**

Adds an internal note to a Pylon issue. Internal notes are not visible to the requester.

- Action

**Add tag**

Creates a new tag in Pylon that can be applied to accounts, articles or issues.

- Action

**Add task**

Creates a task in Pylon with a title and optional details such as assignee, due date, account, project and status. Returns the new task.

- Action

**Create Account**

Creates a new customer account in Pylon with its name, domains, owner, tags and other details.

- Action

**Create Account Activity**

Creates a custom activity on a Pylon account's timeline.

- Action

**Create Call Recording**

Creates a call recording in Pylon from your own call recorder, including its transcript, and returns the new recording. Requires the Custom Call Recorder integration to be enabled in Pylon.

- Action

**Delete account**

Permanently deletes a Pylon account by its ID or external ID.

- Action

**Delete issue**

Permanently deletes an issue in Pylon.

- Action

**Find Account by Name**

Finds Pylon accounts by name, by exact or partial match, returning the matching accounts.

- Action

**Find contacts by criteria**

Returns the contacts that match the specified search text and/or filter.

- Action

**Find issues by criteria**

Returns Pylon issues matching a text search and/or a filter on fields such as state, assignee, account, tags or dates.

- Action

**Get account**

Returns a single Pylon account by its ID or external ID, including its domains, owner, tags, channels and custom fields.

- Action

**Get contact**

Returns a single contact, including its emails, phone numbers, account and custom field values, by its ID or external ID.

- Action

**Get issue**

Returns a single Pylon issue by its ID or issue number, including its custom field values. An error occurs if the issue is not found.

- Action

**Get user**

Returns a single Pylon team member by ID, including their name, email addresses, status, and assigned roles.

- Action

**Get Users**

Returns the users in your Pylon organization, optionally including deactivated users.

- Action

**List accounts**

Returns all accounts in your Pylon organization, including their domains, owner, tags and custom field values.

- Action

**List contacts**

Returns all contacts in the Pylon organization, including their emails, phone numbers, account and custom field values.

- Action

**List tags**

Returns all tags in the Pylon organization, with each tag's name, color and the type of object it applies to.

- Action

**List teams**

Returns all teams in the Pylon organization, with their members, how each team assigns issues, and any recurring assignment schedule.

- Action

**Reply to issue**

Sends a customer-facing reply on a Pylon issue, continuing an existing conversation or thread. Returns the ID of the new message and its issue.

- Action

**Update Account**

Updates an existing Pylon account. Only the fields you fill in are changed.

- Action

**Update contact**

Updates an existing Pylon contact by its ID or external ID. Only the fields you fill in are changed.

- Action

**Update issue**

Updates an existing Pylon issue — its title, state, assignee, team, account, requester, tags, type, portal visibility and custom fields. Only the fields you fill in are changed.

- Action

**Update Issue Followers**

Adds or removes users and contacts as followers of a Pylon issue, and returns the issue's resulting followers.

## 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)
- [ **Pylon** Pylon is a modern, powerful support system built for B2B.](https://apiant.ai/connections/pylon)

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 Pylon

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

Questions

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

Any of Pylon's 25 actions, including Create Account, Create Account Activity, Create Call Recording and Update Account. Your agent maps the data both ways and tests every scenario before it ships.

###

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

Pylon has no triggers in the catalog today, so automations start in Azure DevOps. If you need the other direction, ask: your agent reads Pylon's API documentation and adds it.

###

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

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 Pylon 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.
