--- title: "Connect Azure Service Bus and v0.dev - APIANT.ai" description: "When \"New Message in Queue\" fires in Azure Service Bus, your agent runs \"Send Message\" in v0.dev." canonical: "https://apiant.ai/connect/azure-service-bus-to-v0-dev" --- # Connect Azure Service Bus and v0.dev When **New Message in Queue** fires in [Azure Service Bus](https://apiant.ai/connections/azure-service-bus), your agent runs **Send Message** in [v0.dev](https://apiant.ai/connections/v0-dev), or **New Chat** in v0.dev 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 v0.dev **2** triggers v0.dev **12** 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 v0.dev 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 v0.dev can do together ### From Azure Service Bus to v0.dev - When **New Message in Queue** in Azure Service Bus then **Send Message** in v0.dev - When **New Message in Queue** in Azure Service Bus then **List chat messages** in v0.dev ### From v0.dev to Azure Service Bus - When **New Chat** in v0.dev then **Send Message to Queue** in Azure Service Bus - When **New Project** in v0.dev 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 v0.dev ## Triggers and actions 3 triggers · 21 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 **New Chat** Triggers when a new chat is created. - Trigger **New Project** Triggers when a new project is created. - Action **Create Chat** Create a new chat with v0 to generate code, components, or applications. - Action **Create Project** Creates a new v0 project with an optional description, icon, environment variables, and instructions. Projects help organize chats and manage context. - Action **Delete Chat** Deletes an existing v0 chat using its chatId. This action is irreversible and will remove the chat and all associated data. - Action **Delete Project** Deletes an existing v0 project using its projectId. This action is irreversible and will remove the project and all associated data. - Action **Get chat** Retrieve a chat by id. - Action **Get project** Retrieve a project by id. - Action **List chat messages** List messages in a chat. - Action **List chats** List all chats. - Action **List projects** List all projects. - Action **Send Message** Send a message to an existing chat in v0. - Action **Update Chat** Updates the metadata of an existing chat using its chatId. Supports changes to the chat name and privacy setting. - Action **Update Project** Updates the metadata of an existing project using its projectId. Supports changes to the project name, description, instructions, and privacy setting. ## 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) - [ **v0.dev** v0.dev is a pair programmer that lets you describe your ideas in natural language and generates both the...](https://apiant.ai/connections/v0-dev) 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 v0.dev - [ **Every.org to v0.dev** Every.org is a nonprofit that simplifies modern fundraising for charitable organizations of all sizes.](https://apiant.ai/connect/every-org-to-v0-dev) - [ **HubSpot to v0.dev** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-v0-dev) - [ **Salesforce to v0.dev** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-v0-dev) - [ **Slack to v0.dev** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-v0-dev) - [ **Google Sheets to v0.dev** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-v0-dev) - [ **Gmail to v0.dev** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-v0-dev) Questions ## Azure Service Bus and v0.dev, 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 v0.dev when something happens in Azure Service Bus? Any of v0.dev's 12 actions, including Create Chat, Create Project, Send Message and Update Chat. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from v0.dev to Azure Service Bus? Yes. When something happens in v0.dev, your agent can act in Azure Service Bus too. This page covers both directions: v0.dev'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 v0.dev? 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 v0.dev 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.