--- title: "Connect Azure Service Bus to HitPay - APIANT.ai" description: "When \"New Message in Queue\" fires in Azure Service Bus, your agent runs \"Add customer\" in HitPay." canonical: "https://apiant.ai/connect/azure-service-bus-to-hitpay" --- # Connect Azure Service Bus to HitPay When **New Message in Queue** fires in [Azure Service Bus](https://apiant.ai/connections/azure-service-bus), your agent runs **Add customer** in [HitPay](https://apiant.ai/connections/hitpay). 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 HitPay **22** 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 HitPay 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 HitPay - When **New Message in Queue** in Azure Service Bus then **Add customer** in HitPay - When **New Message in Queue** in Azure Service Bus then **Add order** in HitPay 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 HitPay ## Triggers and actions 1 trigger · 31 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 **Add customer** Creates a customer in your HitPay account with their contact details and optional address. - Action **Add order** Creates a new draft order in HitPay. - Action **Add subscription plan** Creates a subscription plan with a name, amount and billing frequency that customers can be signed up to for recurring billing. - Action **Create Payment Request** Creates a HitPay payment request and returns its checkout link for the buyer to pay. - Action **Delete customer** Deletes a customer from your HitPay account. - Action **Delete invoice** Deletes an invoice from your HitPay business account. - Action **Delete Payment Request** Deletes a payment request. Completed payment requests cannot be deleted. - Action **Delete product** Deletes a product from your HitPay product catalog. - Action **Get balances** Returns your HitPay account balances for each currency, including available, pending and reserve amounts. - Action **Get charge** Returns the details of a single HitPay charge, including amount, fees, status, payment method, customer and refunds. - Action **Get customer** Returns the details of a HitPay customer, including contact information and address. - Action **Get order** Returns the full details of a HitPay order, including its line items, charges, customer and totals. - Action **Get Payment Request Details** Returns a payment request's details and status, including its amount, customer, checkout URL and any payments made against it. - Action **Get product** Returns the details of a product, including its price, variations and images. - Action **List charges** Returns the charges (payments) on your HitPay account, optionally filtered by status, date, amount, customer, payment request or payout. - Action **List customers** Returns all customers saved in your HitPay account. - Action **List invoices** Returns the invoices in your HitPay account, optionally filtered by customer email, status or reference. - Action **List payouts** Returns payouts of your HitPay balance to your linked bank account, newest first, optionally filtered by status and creation date. - Action **List products** Returns the products in your HitPay account, optionally filtered by status, category, source, inventory, location, channel or keyword. - Action **Refund Payment** Refunds all or part of a successful payment, returning the refund record. - Action **Update customer** Updates an existing customer's details, such as name, email, phone and address. - Action **Update product** Updates an existing product in your HitPay store, such as its name, price, stock, categories and variations. ## 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) - [ **HitPay** HitPay is a one-stop payments and commerce platform for SMEs.](https://apiant.ai/connections/hitpay) 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 HitPay - [ **HubSpot to HitPay** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-hitpay) - [ **Salesforce to HitPay** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-hitpay) - [ **Slack to HitPay** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-hitpay) - [ **Google Sheets to HitPay** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-hitpay) - [ **Gmail to HitPay** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-hitpay) - [ **Google Calendar to HitPay** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-hitpay) Questions ## Azure Service Bus and HitPay, 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 HitPay when something happens in Azure Service Bus? Any of HitPay's 22 actions, including Create Payment Request, Update customer, Update product and Add customer. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from HitPay to Azure Service Bus? HitPay has no triggers in the catalog today, so automations start in Azure Service Bus. If you need the other direction, ask: your agent reads HitPay's API documentation and adds it. ### ### Do I have to build a connector for Azure Service Bus or HitPay? 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 HitPay 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.