--- title: "Connect Azure Service Bus to Slite - APIANT.ai" description: "When \"New Message in Queue\" fires in Azure Service Bus, your agent runs \"Verify note\" in Slite." canonical: "https://apiant.ai/connect/azure-service-bus-to-slite" --- # Connect Azure Service Bus to Slite When **New Message in Queue** fires in [Azure Service Bus](https://apiant.ai/connections/azure-service-bus), your agent runs **Verify note** in [Slite](https://apiant.ai/connections/slite). 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 Slite **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 Slite 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 can start in Slite - When **New Message in Queue** in Azure Service Bus then **Verify note** in Slite - When **New Message in Queue** in Azure Service Bus then **Create Doc** in Slite 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 Slite ## Triggers and actions 1 trigger · 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. - Action **Archive note** Archives a Slite note, or restores an archived note, and returns the updated note. - Action **Ask Question** Asks a question in natural language and returns an answer drawn from the Slite notes the connected user can access, along with the notes used as sources. - Action **Create Doc** Creates a new Slite doc from Markdown, HTML or SliteML content, a template, or as an empty doc, and returns the created doc. - Action **Delete note** Permanently deletes a note and all of its child notes by ID. This cannot be undone. - Action **Fetch Doc** Returns a Slite doc by its ID, including its title, content, location, review state and any collection attributes. - Action **Fetch Sub Docs** Returns the sub-docs of a Slite doc: its direct children, or its whole subtree when descendants are included. - Action **Find groups by query** Returns the Slite groups whose name matches the search text you provide. - Action **Find users by query** Returns the users whose email address or display name matches the search text. - Action **Get group** Returns a Slite group's name and description by its ID. - Action **Get user** Returns a Slite user's display name, email address, organization role, guest status and archived date. - Action **Index AskX Object** Adds or refreshes a piece of custom content in a Slite custom data source so it can be used by Ask. Returns the indexed object's id, title, URL and last update date. - Action **List notes** Returns the notes in a Slite workspace, optionally filtered by owner or parent note and sorted by last edit or sidebar position. - Action **Replace Doc** Replaces a doc's content with new Markdown, HTML or SliteML, and can also change its title, collection attributes and sidebar position. Returns the updated doc. - Action **Search Docs** Returns the docs that match a search text, with optional filters for parent doc, depth, review state, edit dates and archived status. - Action **Update Doc** Updates a doc's title, content, collection attributes or sidebar position, and returns the updated doc. - Action **Verify note** Marks a Slite note as Verified, with an optional date when the verification expires, and returns the updated note. ## 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) - [ **Slite** Slite is an AI-powered knowledge base for teams that combines powerful knowledge management features with...](https://apiant.ai/connections/slite) 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 Slite - [ **HubSpot to Slite** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-slite) - [ **Salesforce to Slite** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-slite) - [ **Slack to Slite** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-slite) - [ **Google Sheets to Slite** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-slite) - [ **Gmail to Slite** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-slite) - [ **Google Calendar to Slite** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-slite) Questions ## Azure Service Bus and Slite, 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 Slite when something happens in Azure Service Bus? Any of Slite's 16 actions, including Create Doc, Update Doc, Ask Question and Fetch Doc. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Slite to Azure Service Bus? Slite has no triggers in the catalog today, so automations start in Azure Service Bus. If you need the other direction, ask: your agent reads Slite's API documentation and adds it. ### ### Do I have to build a connector for Azure Service Bus or Slite? 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 Slite 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.