---
title: "Connect Azure DevOps to Flodesk - APIANT.ai"
description: "When \"Completed Build\" fires in Azure DevOps, your agent runs \"Find a Subscriber by Email Address\" in Flodesk."
canonical: "https://apiant.ai/connect/azure-devops-to-flodesk"
---

# Connect Azure DevOps to Flodesk

When **Completed Build** fires in [Azure DevOps](https://apiant.ai/connections/azure-devops), your agent runs **Find a Subscriber by Email Address** in [Flodesk](https://apiant.ai/connections/flodesk). Describe the whole flow and it is built, tested on every scenario and kept running.

Azure DevOps **5** triggers Azure DevOps **5** actions Flodesk **15** 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 Flodesk 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 Flodesk

- When **Completed Build** in Azure DevOps then **Find a Subscriber by Email Address** in Flodesk
- When **New Work Item** in Azure DevOps then **Add custom field** in Flodesk

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 Flodesk

## Triggers and actions 5 triggers · 20 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 custom field**

Creates a new subscriber custom field in your Flodesk account with the label you choose.

- Action

**Add Existing Subscriber to Segment**

Adds an existing Flodesk subscriber to one or more segments and returns the updated subscriber.

- Action

**Add Existing Subscriber to Workflow**

Adds an existing Flodesk subscriber to a workflow, identified by subscriber ID or email address.

- Action

**Add segment**

Creates a new segment in your Flodesk account and returns it.

- Action

**Create/Update Subscriber**

Creates a new Flodesk subscriber, or updates the existing one with the same email address or id, optionally adding them to segments.

- Action

**Find a Subscriber by Email Address**

Looks up a Flodesk subscriber by email address and returns their status, name, segments and custom field values.

- Action

**Get segment**

Returns a single Flodesk segment, including its name, color, type and number of active subscribers.

- Action

**List campaigns**

Returns the email campaigns in your Flodesk account, optionally filtered by status or a search term.

- Action

**List custom fields**

Returns every subscriber custom field defined in your Flodesk account, with each field's key and display label.

- Action

**List segments**

Returns all segments in your Flodesk account, with each segment's name, color, type and active subscriber count.

- Action

**List subscribers**

Returns subscribers in your Flodesk account, optionally filtered by status or segment.

- Action

**List workflows**

Returns the workflows in your Flodesk account, optionally filtered by status (active, paused or draft).

- Action

**Remove Existing Subscriber From Segment**

Removes an existing Flodesk subscriber from one or more segments and returns the updated subscriber.

- Action

**Remove Existing Subscriber From Workflow**

Removes an existing subscriber, identified by subscriber ID or email address, from a Flodesk workflow.

- Action

**Unsubscribe Subscriber**

Unsubscribes a subscriber from all of your Flodesk lists so they no longer receive marketing emails, and returns the updated subscriber.

## 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)
- [ **Flodesk** Beginners and experts use Flodesk to create stunning emails that grow their business.](https://apiant.ai/connections/flodesk)

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 Flodesk

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

Questions

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

Any of Flodesk's 15 actions, including Create/Update Subscriber, Add custom field, Add Existing Subscriber to Segment and Add Existing Subscriber to Workflow. Your agent maps the data both ways and tests every scenario before it ships.

###

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

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

###

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

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