--- title: "Connect Azure DevOps and Request Tracker (RT) - APIANT.ai" description: "When \"Completed Build\" fires in Azure DevOps, your agent runs \"Create Ticket\" in Request Tracker (RT)." canonical: "https://apiant.ai/connect/azure-devops-to-request-tracker-rt" --- # Connect Azure DevOps and Request Tracker (RT) When **Completed Build** fires in [Azure DevOps](https://apiant.ai/connections/azure-devops), your agent runs **Create Ticket** in [Request Tracker (RT)](https://apiant.ai/connections/request-tracker-rt), or **Ticket Created** in Request Tracker (RT) 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 Request Tracker (RT) **3** triggers Request Tracker (RT) **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 Request Tracker (RT) 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 Request Tracker (RT) can do together ### From Azure DevOps to Request Tracker (RT) - When **Completed Build** in Azure DevOps then **Create Ticket** in Request Tracker (RT) - When **New Work Item** in Azure DevOps then **Update ticket** in Request Tracker (RT) ### From Request Tracker (RT) to Azure DevOps - When **Ticket Created** in Request Tracker (RT) then **Add Link to Work Item** in Azure DevOps - When **Ticket Status Changed** in Request Tracker (RT) 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 Request Tracker (RT) ## Triggers and actions 8 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 **Ticket Correspondence** Triggers when a ticket is replied to (that is, corresponded with). - Trigger **Ticket Created** Triggers when a new Request Tracker ticket is created. - Trigger **Ticket Status Changed** Triggers when a Request Tracker ticket changes status. Can watch for any status change or only for changes to a specific status. - Action **Add asset** Create an asset. - Action **Comment on a Ticket** Add an internal comment to a ticket and send to any internal watchers. - Action **Create Ticket** Create a new ticket in Request Tracker. - Action **Find Attachment** Locate an attachment by ID. - Action **Find Ticket** Locate a ticket by ID. - Action **Find Tickets** Issue a query to find matching tickets. - Action **Find Transaction** Find a transaction by ID - Action **Get asset** Retrieves one asset by ID: name, description, status, catalog, owner, held by, contact, custom fields. - Action **Get queue** Get a queue by id or name. - Action **Get user** Get a user by id or name. - Action **List queues** List all queues visible to user. - Action **List ticket history** List transactions of a ticket. - Action **Reply to a Ticket** Reply to the requestor and any internal or external watchers of a ticket. - Action **Update ticket** General ticket update (Owner, Priority, Queue, custom fields). - Action **Update Ticket Due Date** Update the due date of a ticket. - Action **Update Ticket Status** Update the status of a ticket. - Action **Update Ticket Subject** Update the subject of a ticket. - Action **Update user** Update a user. ## 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) - [ **Request Tracker (RT)** Request Tracker (RT) is an open-source, enterprise-grade ticketing system.](https://apiant.ai/connections/request-tracker-rt) 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 Request Tracker (RT) - [ **HubSpot to Request Tracker (RT)** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-request-tracker-rt) - [ **Google Sheets to Request Tracker (RT)** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-request-tracker-rt) - [ **Gmail to Request Tracker (RT)** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-request-tracker-rt) - [ **Google Calendar to Request Tracker (RT)** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-request-tracker-rt) - [ **Google Drive to Request Tracker (RT)** Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...](https://apiant.ai/connect/google-drive-to-request-tracker-rt) - [ **Mailchimp to Request Tracker (RT)** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/mailchimp-to-request-tracker-rt) Questions ## Azure DevOps and Request Tracker (RT), 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 Request Tracker (RT) when something happens in Azure DevOps? Any of Request Tracker (RT)'s 18 actions, including Create Ticket, Update ticket, Update Ticket Due Date and Update Ticket Status. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Request Tracker (RT) to Azure DevOps? Yes. When something happens in Request Tracker (RT), your agent can act in Azure DevOps too. This page covers both directions: Request Tracker (RT)'s triggers and Azure DevOps's actions are listed here as well. ### ### Do I have to build a connector for Azure DevOps or Request Tracker (RT)? 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 Request Tracker (RT) 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.