--- title: "Connect Azure DevOps and Trengo - APIANT.ai" description: "When \"Completed Build\" fires in Azure DevOps, your agent runs \"Add internal note to ticket\" in Trengo." canonical: "https://apiant.ai/connect/azure-devops-to-trengo" --- # Connect Azure DevOps and Trengo When **Completed Build** fires in [Azure DevOps](https://apiant.ai/connections/azure-devops), your agent runs **Add internal note to ticket** in [Trengo](https://apiant.ai/connections/trengo), or **New Internal Note** in Trengo 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 Trengo **3** triggers Trengo **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 Trengo 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 Trengo can do together ### From Azure DevOps to Trengo - When **Completed Build** in Azure DevOps then **Add internal note to ticket** in Trengo - When **New Work Item** in Azure DevOps then **Add ticket** in Trengo ### From Trengo to Azure DevOps - When **New Internal Note** in Trengo then **Add Link to Work Item** in Azure DevOps - When **New Outbound Message** in Trengo 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 Trengo ## Triggers and actions 8 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. - Trigger **New Internal Note** Fires when an internal note is added to a Trengo ticket. - Trigger **New Outbound Message** Triggers when an outbound message is created. - Trigger **Ticket Label Added** Triggers when a label is added to a conversation. - Action **Add internal note to ticket** Adds an internal note (visible only to agents) to a Trengo ticket. - Action **Add ticket** Create a new support ticket. - Action **Add ticket label** Attaches an existing label to a Trengo ticket. - Action **Create a Contact** Creates a contact on a Trengo channel. If a contact with the same identifier already exists on that channel, Trengo returns the existing contact instead of creating a duplicate. - Action **Create webhook** Subscribes a URL to one Trengo webhook event type. Used by Trengo instant triggers to register their delivery URL on activation. - Action **Delete contact** Delete a contact by id. - Action **Delete ticket** Delete a ticket by id. - Action **Find a Contact** Returns the Trengo contacts that match the search term. - Action **Get contact** Retrieve a single Trengo contact by its id. - Action **Get webhook** Fetches a webhook by ID, including the event it listens for, the address it sends to and its signing secret. An error occurs if the webhook is not found. - Action **List contacts** List all contacts. - Action **List labels** Lists the ticket labels defined in the Trengo account (first page). - Action **List tickets** Returns all tickets the connected user is authorized to see, optionally filtered by status, contact, users, channels, labels, last message type or update time. - Action **Send a Message** Sends a reply message on an existing Trengo ticket, over the ticket's own channel. - Action **Update contact** Update an existing contact by id. ## 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) - [ **Trengo** Trengo is a team collaboration tool to manage conversations from channels such as web chat, email and...](https://apiant.ai/connections/trengo) 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 Trengo - [ **OpenAI to Trengo** OpenAI's platform for text generation (Responses + Chat Completions), image generation (gpt-image-1 /...](https://apiant.ai/connect/openai-to-trengo) - [ **CloudConvert to Trengo** CloudConvert converts files between more than 200 supported formats: documents, image, spreadsheet...](https://apiant.ai/connect/cloudconvert-to-trengo) - [ **elmah.io to Trengo** Cloud logging for.NET web applications using ELMAH.](https://apiant.ai/connect/elmah-io-to-trengo) - [ **Postman to Trengo** Postman is a platform for building and testing APIs.](https://apiant.ai/connect/postman-to-trengo) - [ **HubSpot to Trengo** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-trengo) - [ **Salesforce to Trengo** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-trengo) Questions ## Azure DevOps and Trengo, 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 Trengo when something happens in Azure DevOps? Any of Trengo's 15 actions, including Create a Contact, Create webhook, Send a Message and Update contact. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Trengo to Azure DevOps? Yes. When something happens in Trengo, your agent can act in Azure DevOps too. This page covers both directions: Trengo's triggers and Azure DevOps's actions are listed here as well. ### ### Do I have to build a connector for Azure DevOps or Trengo? 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 Trengo 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.