---
title: "Connect Azure DevOps to Fly.io Machines API - APIANT.ai"
description: "When \"Completed Build\" fires in Azure DevOps, your agent runs \"Create App\" in Fly.io Machines API."
canonical: "https://apiant.ai/connect/azure-devops-to-fly-io-machines-api"
---

# Connect Azure DevOps to Fly.io Machines API

When **Completed Build** fires in [Azure DevOps](https://apiant.ai/connections/azure-devops), your agent runs **Create App** in [Fly.io Machines API](https://apiant.ai/connections/fly-io-machines-api). Describe the whole flow and it is built, tested on every scenario and kept running.

Azure DevOps **5** triggers Azure DevOps **5** actions Fly.io Machines API **11** 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 Fly.io Machines API 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 Fly.io Machines API

- When **Completed Build** in Azure DevOps then **Create App** in Fly.io Machines API
- When **New Work Item** in Azure DevOps then **Create Machine** in Fly.io Machines API

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 Fly.io Machines API

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

**Create App**

Creates a new Fly.io app in the chosen organization and returns its id.

- Action

**Create Machine**

Creates a new Machine in a Fly.io app from the image and configuration you provide, and returns the created Machine.

- Action

**Create Volume**

Creates a persistent storage volume for a Fly.io app in the chosen region.

- Action

**Delete App**

Deletes a Fly.io app by its name.

- Action

**Delete Machine**

Deletes a Machine from a Fly.io app, optionally force-killing it if it is still running.

- Action

**Delete Volume**

Destroys a volume in a Fly.io app and returns the deleted volume's details.

- Action

**Extend Volume**

Extends a Fly.io volume to a larger size in gigabytes. Returns the updated volume and whether its Machine needs a restart.

- Action

**Start Machine**

Starts a stopped or suspended Machine in a Fly.io app.

- Action

**Stop Machine**

Stops a running Fly.io Machine in an app, optionally choosing the stop signal and how long to wait before it is killed.

- Action

**Suspend Machine**

Suspends a Machine in a Fly.io app so its next start can resume from a snapshot instead of a cold boot.

- Action

**Update Machine**

Updates a Fly.io Machine's configuration, such as its image, guest size, environment variables, services or restart policy, and returns the updated Machine.

## 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)
- [ **Fly.io Machines API** Fly.io Machines API is a low-level interface to deploy and manage lightweight VMs globally with fine-grained...](https://apiant.ai/connections/fly-io-machines-api)

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 Fly.io Machines API

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

Questions

## Azure DevOps and Fly.io Machines API, 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 Fly.io Machines API when something happens in Azure DevOps?

Any of Fly.io Machines API's 11 actions, including Create App, Create Machine, Create Volume and Update Machine. Your agent maps the data both ways and tests every scenario before it ships.

###

### Can it also run from Fly.io Machines API to Azure DevOps?

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

###

### Do I have to build a connector for Azure DevOps or Fly.io Machines API?

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 Fly.io Machines API 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.
