--- title: "Connect Azure Service Bus and Returnless - APIANT.ai" description: "When \"New Message in Queue\" fires in Azure Service Bus, your agent runs \"Find customers\" in Returnless." canonical: "https://apiant.ai/connect/azure-service-bus-to-returnless" --- # Connect Azure Service Bus and Returnless When **New Message in Queue** fires in [Azure Service Bus](https://apiant.ai/connections/azure-service-bus), your agent runs **Find customers** in [Returnless](https://apiant.ai/connections/returnless), or **Request Created** in Returnless 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 Returnless **2** triggers Returnless **16** 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 Returnless 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 Returnless can do together ### From Azure Service Bus to Returnless - When **New Message in Queue** in Azure Service Bus then **Find customers** in Returnless - When **New Message in Queue** in Azure Service Bus then **Add note** in Returnless ### From Returnless to Azure Service Bus - When **Request Created** in Returnless then **Send Message to Queue** in Azure Service Bus - When **Return Created** in Returnless 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 Returnless ## Triggers and actions 3 triggers · 25 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 **Request Created** Triggers when a customer creates a new return request that needs approval. - Trigger **Return Created** Triggers when a new return is created, including a request once it is approved. - Action **Add note** Adds an internal note to a return or return request. - Action **Add Request** Creates a return request in Returnless for items from an existing sales order. - Action **Approve a Request** Approves a return request in Returnless so the customer can send the items back. - Action **Approve a Request Without Shipment** Approves a pending return request without a return shipment, so the customer keeps the items. - Action **Find customers** Returns the customers in your Returnless account that match an email address. - Action **Find products** Returns the products in your Returnless account that match a SKU. - Action **Find Requests** Finds a Request in your Returnless account. - Action **Find Returns** Finds returns (return orders) in Returnless by return number. - Action **Find sales orders** Finds sales orders in Returnless by order number. - Action **Get customer** Returns a single Returnless customer by its id. - Action **Get Request (By Request ID)** Returns a single return request (return order) from Returnless by its ID. - Action **Get Return (By Return ID)** Returns a single return in Returnless, with all of its details, by its return ID. - Action **Get sales order** Returns a single sales order by its ID, including its customer, address and order details. - Action **List return reasons** Returns the return reasons configured in your Returnless account. - Action **Reject Request** Rejects a pending return request in Returnless. - Action **Update return** Changes the status of a return, such as Checked, Approved or Resolved. ## 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) - [ **Returnless** Returnless gives e-commerce businesses a way to get their returns in check.](https://apiant.ai/connections/returnless) 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 Returnless - [ **HubSpot to Returnless** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-returnless) - [ **Google Sheets to Returnless** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-returnless) - [ **Gmail to Returnless** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-returnless) - [ **Google Calendar to Returnless** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-returnless) - [ **Google Drive to Returnless** Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...](https://apiant.ai/connect/google-drive-to-returnless) - [ **Mailchimp to Returnless** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/mailchimp-to-returnless) Questions ## Azure Service Bus and Returnless, 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 Returnless when something happens in Azure Service Bus? Any of Returnless's 16 actions, including Update return, Add note, Add Request and Approve a Request. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Returnless to Azure Service Bus? Yes. When something happens in Returnless, your agent can act in Azure Service Bus too. This page covers both directions: Returnless'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 Returnless? 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 Returnless 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.