--- title: "Connect Azure Service Bus and Willo - APIANT.ai" description: "When \"New Message in Queue\" fires in Azure Service Bus, your agent runs \"Add department\" in Willo." canonical: "https://apiant.ai/connect/azure-service-bus-to-willo" --- # Connect Azure Service Bus and Willo When **New Message in Queue** fires in [Azure Service Bus](https://apiant.ai/connections/azure-service-bus), your agent runs **Add department** in [Willo](https://apiant.ai/connections/willo), or **List Users** in Willo 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 Willo **1** trigger Willo **19** 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 Willo 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 Willo can do together ### From Azure Service Bus to Willo - When **New Message in Queue** in Azure Service Bus then **Add department** in Willo - When **New Message in Queue** in Azure Service Bus then **Add interview from template** in Willo ### From Willo to Azure Service Bus - When **List Users** in Willo then **Send Message to Queue** in Azure Service Bus - When **List Users** in Willo 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 Willo ## Triggers and actions 2 triggers · 28 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 **List Users** Triggers when a new user is added to your Willo account. - Action **Accept Candidate** Marks a participant in a Willo interview as Accepted and returns the updated participant. Can also update the participant's name, phone number and custom ID in the same step. - Action **Add department** Creates a new department in your Willo organisation and returns the department, including its key and branding. - Action **Add interview from template** Creates a new interview in Willo from one of your interview templates and returns the new interview. - Action **Create Company** Creates a new company as a child organisation under your Willo organisation, with the owner you name. - Action **Create Interview** Creates a new video interview in Willo with its questions, department, message templates and settings. - Action **Delete interview** Deletes an interview from your Willo account. - Action **Delete participant** Deletes a participant from Willo. Returns whether the deletion was confirmed. - Action **Get interview** Returns a Willo interview by its key, including its questions, owner, department, reviewers, message templates and settings. An error occurs if the interview is not found. - Action **Get participant** Returns a Willo participant (candidate) with their contact details, status, interview, department, scores and answers. - Action **Get user** Returns a Willo user's details, including email, full name, phone, role and status. - Action **Invite Someone** Invites a person to a Willo interview as a participant and returns the new participant with their invite link. - Action **List departments** Returns the departments in your Willo organisation, optionally filtered by name, owner email or owner. - Action **List interviews** Returns the interviews in your Willo account, optionally narrowed by department, owner or a search term, and sorted the way you choose. - Action **List message templates** Returns the message templates (email and SMS) in your Willo account, optionally filtered by title, type or trigger. - Action **List participants** Returns the participants in your Willo account, optionally narrowed to an interview, department or owner, or by a text search. - Action **List users** Returns the users in your Willo account with their key, email and full name. - Action **Reject Candidate** Rejects a candidate by setting the participant's status to Rejected, optionally updating their name, phone or custom ID. - Action **Update interview** Updates an existing interview's details, questions, reviewers, message templates and settings, changing only the values you provide. Returns the updated interview. - Action **Update participant** Updates a participant's name, phone, status (Accepted or Rejected) or your own reference ID. ## 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) - [ **Willo** Willo helps you get answers to your questions faster with video interviewing.](https://apiant.ai/connections/willo) 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 Willo - [ **HubSpot to Willo** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-willo) - [ **Salesforce to Willo** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-willo) - [ **Slack to Willo** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-willo) - [ **Google Sheets to Willo** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-willo) - [ **Gmail to Willo** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-willo) - [ **Google Calendar to Willo** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-willo) Questions ## Azure Service Bus and Willo, 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 Willo when something happens in Azure Service Bus? Any of Willo's 19 actions, including Create Company, Create Interview, Update interview and Update participant. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Willo to Azure Service Bus? Yes. When something happens in Willo, your agent can act in Azure Service Bus too. This page covers both directions: Willo'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 Willo? 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 Willo 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.