---
title: "Connect Azure DevOps and Concord CLM - APIANT.ai"
description: "When \"Completed Build\" fires in Azure DevOps, your agent runs \"Create a New Document From a Template\" in Concord CLM."
canonical: "https://apiant.ai/connect/azure-devops-to-concord-clm"
---

# Connect Azure DevOps and Concord CLM

When **Completed Build** fires in [Azure DevOps](https://apiant.ai/connections/azure-devops), your agent runs **Create a New Document From a Template** in [Concord CLM](https://apiant.ai/connections/concord-clm), or **New agreement** in Concord CLM 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 Concord CLM **1** trigger Concord CLM **18** 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 Concord CLM 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 Concord CLM can do together

### From Azure DevOps to Concord CLM

- When **Completed Build** in Azure DevOps then **Create a New Document From a Template** in Concord CLM
- When **New Work Item** in Azure DevOps then **Create an Executed Document** in Concord CLM

### From Concord CLM to Azure DevOps

- When **New agreement** in Concord CLM then **Add Link to Work Item** in Azure DevOps
- When **New agreement** in Concord CLM 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 Concord CLM

## Triggers and actions 6 triggers · 23 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 agreement**

Triggers when a new agreement appears in the selected Concord organization.

- Action

**Add agreement**

Creates a new agreement in a Concord organization, either as a blank draft, template or contract, or from an existing template or contract. Returns the new agreement's identifiers.

- Action

**Add attachment**

Uploads a file and attaches it to a Concord agreement, and returns the ID of the new attachment.

- Action

**Add folder**

Creates a new folder inside an existing folder of a Concord organization and returns the new folder.

- Action

**Add member to agreement**

Invites a person to an agreement by email with the chosen permission level and sends them an invitation message. Returns the agreement's id, unique identifier and status.

- Action

**Create a New Document From a Template**

Creates a new Concord document from an automated template, filling in its variables and optionally inviting people to it.

- Action

**Create an Executed Document**

Creates an agreement in Concord with the status of an executed contract, rather than a draft or template. Returns the new agreement's identifiers.

- Action

**Create webhook - Document Fully Approved**

Creates a Concord webhook integration that calls the given URL when an agreement is fully approved.

- Action

**Create webhook - Document Fully Signed**

Creates a Concord webhook integration that calls the given address when an agreement is fully signed.

- Action

**Create webhook - Signature Provided**

Creates a Concord webhook integration that calls the given address whenever a new signature is added to an agreement.

- Action

**Delete agreement**

Permanently deletes an agreement from a Concord organization.

- Action

**Get agreement**

Returns one Concord agreement by its UID, including its title, status, folder, tags, permission and creation details. An error occurs if the agreement is not found.

- Action

**List agreements**

Returns the agreements in a Concord organization's inbox, filtered by stage and optionally by creator, tags, dates, parties and search text.

- Action

**List automated templates**

Returns the automated templates available in a Concord organization, with each template's id, title and description.

- Action

**List folders**

Returns the folder tree of a Concord organization: the root folder with its nested subfolders, access settings and document counts.

- Action

**List organizations**

Returns every Concord organization the connected user belongs to, including each organization's name, subscription, and the user's role in it.

- Action

**Move agreement**

Moves an agreement into a different folder in a Concord organization.

- Action

**Request signature**

Requests signatures on an agreement from its signers. Colleagues are added to the agreement, external signers are emailed an invitation, and when a signing order is enabled the request goes to the next signer in that order.

- Action

**Update agreement**

Updates the status of an existing Concord agreement, setting it to Signing or Broken.

## 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)
- [ **Concord CLM** Concord is a full contract lifecycle management platform with drafting, approvals, e-signature and storage -...](https://apiant.ai/connections/concord-clm)

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 Concord CLM

- [ **ActiveCampaign to Concord CLM** ActiveCampaign is a marketing automation, email marketing, and CRM platform.](https://apiant.ai/connect/activecampaign-to-concord-clm)
- [ **Airtable to Concord CLM** Organize anything with Airtable, a modern database created for everyone.](https://apiant.ai/connect/airtable-to-concord-clm)
- [ **Asana to Concord CLM** Asana is a collaborative information manager for workspace.](https://apiant.ai/connect/asana-to-concord-clm)
- [ **ClickUp to Concord CLM** 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-concord-clm)
- [ **Brevo to Concord CLM** Brevo is the leading CRM suite designed to cultivate long-term customer relationships and help businesses...](https://apiant.ai/connect/brevo-to-concord-clm)
- [ **Calendly to Concord CLM** Calendly is a scheduling automation platform for eliminating the back-and-forth emails to find the perfect...](https://apiant.ai/connect/calendly-to-concord-clm)

Questions

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

Any of Concord CLM's 18 actions, including Create a New Document From a Template, Create an Executed Document, Create webhook - Document Fully Approved and Create webhook - Document Fully Signed. Your agent maps the data both ways and tests every scenario before it ships.

###

### Can it also run from Concord CLM to Azure DevOps?

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

###

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

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 Concord CLM 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.
