--- title: "Connect Azure Service Bus and Request Tracker (RT) - APIANT.ai" description: "When \"New Message in Queue\" fires in Azure Service Bus, your agent runs \"Create Ticket\" in Request Tracker (RT)." canonical: "https://apiant.ai/connect/azure-service-bus-to-request-tracker-rt" --- # Connect Azure Service Bus and Request Tracker (RT) When **New Message in Queue** fires in [Azure Service Bus](https://apiant.ai/connections/azure-service-bus), your agent runs **Create Ticket** in [Request Tracker (RT)](https://apiant.ai/connections/request-tracker-rt), or **Ticket Created** in Request Tracker (RT) to **Send Message to Queue** in Azure Service Bus. Describe the whole flow and it is built, tested on every scenario and kept running. Azure Service Bus **1** trigger Azure Service Bus **9** 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 Service Bus 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 Service Bus and Request Tracker (RT) can do together ### From Azure Service Bus to Request Tracker (RT) - When **New Message in Queue** in Azure Service Bus then **Create Ticket** in Request Tracker (RT) - When **New Message in Queue** in Azure Service Bus then **Update ticket** in Request Tracker (RT) ### From Request Tracker (RT) to Azure Service Bus - When **Ticket Created** in Request Tracker (RT) then **Send Message to Queue** in Azure Service Bus - When **Ticket Status Changed** in Request Tracker (RT) then **Abandon Message** in Azure Service Bus 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 Service Bus and Request Tracker (RT) ## Triggers and actions 4 triggers · 27 actions - Trigger **New Message in Queue** Triggers when a message arrives in a Service Bus queue. Each check picks up the next message and removes it from the queue, so use a queue dedicated to this automation. - Action **Abandon Message** Abandons a message received with Receive Message (Peek-Lock), releasing its lock so it can be received again. - Action **Complete Message** Completes a message received with Receive Message (Peek-Lock), removing it from the queue. - Action **Create Queue** Creates a new queue in the connected Service Bus namespace and returns its settings. - Action **Delete Queue** Deletes a queue from the connected Service Bus namespace, along with all of its messages. - Action **Get Queue** Returns a Service Bus queue's settings and its current message counts. - Action **List Queues** Returns the queues in the connected Service Bus namespace, with each queue's status and message counts. - Action **Receive and Delete Message** Receives the next message from a queue in the connected Service Bus namespace and removes it from the queue. - Action **Receive Message (Peek-Lock)** Receives the next message from a queue and locks it, so another receiver cannot take it. Complete the message to remove it, or abandon it to release it back to the queue; the lock expires on its own after the queue's lock duration. - Action **Send Message to Queue** Sends a message to a queue in the connected Service Bus namespace, with optional subject, IDs, scheduling and custom properties. - 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 Service Bus** Managed message broker providing queues and pub/sub topics for reliable, asynchronous communication between...](https://apiant.ai/connections/azure-service-bus) - [ **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 Service Bus - [ **Azure Service Bus to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/azure-service-bus-to-hubspot) - [ **Azure Service Bus to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/azure-service-bus-to-salesforce) - [ **Azure Service Bus to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/azure-service-bus-to-slack) - [ **Azure Service Bus to Google Sheets** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/azure-service-bus-to-google-sheets) - [ **Azure Service Bus to Gmail** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/azure-service-bus-to-gmail) - [ **Azure Service Bus to Google Calendar** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/azure-service-bus-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 Service Bus and Request Tracker (RT), answered ### ### What can start an automation from Azure Service Bus? Any of Azure Service Bus's 1 trigger in the catalog, including New Message in Queue. 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 Service Bus? 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 Service Bus? Yes. When something happens in Request Tracker (RT), your agent can act in Azure Service Bus too. This page covers both directions: Request Tracker (RT)'s triggers and Azure Service Bus's actions are listed here as well. ### ### Do I have to build a connector for Azure Service Bus 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 Service Bus 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.