Integration
Connect Azure Service Bus to Dixa
When New Message in Queue fires in Azure Service Bus, your agent runs Set Custom Contact Attributes in Dixa. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Azure Service Bus and Dixa to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne 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.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)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)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)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)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)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)Example flows
What Azure Service Bus can start in Dixa
When New Message in Queue in Azure Service Bus
then Set Custom Contact Attributes in Dixa
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 Dixa
Triggers and actions 1 trigger · 33 actions
- 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.
- Abandon Message
Abandons a message received with Receive Message (Peek-Lock), releasing its lock so it can be received again.
- Complete Message
Completes a message received with Receive Message (Peek-Lock), removing it from the queue.
- Create Queue
Creates a new queue in the connected Service Bus namespace and returns its settings.
- Delete Queue
Deletes a queue from the connected Service Bus namespace, along with all of its messages.
- Get Queue
Returns a Service Bus queue's settings and its current message counts.
- List Queues
Returns the queues in the connected Service Bus namespace, with each queue's status and message counts.
- Receive and Delete Message
Receives the next message from a queue in the connected Service Bus namespace and removes it from the queue.
- 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.
- Send Message to Queue
Sends a message to a queue in the connected Service Bus namespace, with optional subject, IDs, scheduling and custom properties.
- Add Internal Note
Adds an internal note, visible only to agents, to a Dixa conversation and returns the created note.
- Anonymize Data
Requests the anonymization of a Dixa end user, conversation, or single message, and returns the status of the anonymization request.
- Change Conversation Status
Changes a conversation's status by closing it, reopening it, or putting it into follow-up until a chosen time.
- Create Callback Request
Creates a callback request conversation in Dixa, placing a call-back for an end user into the chosen queue, and returns the new conversation's id.
- Create Conversation
Creates a new Dixa conversation on the email, contact form, chat, SMS, WhatsApp or callback channel and returns its ID.
- Create User
Creates an end user (contact) in Dixa with their name, contact details and any custom contact attributes, and returns the new end user.
- Get Anonymization Status
Returns the status of an anonymization request submitted earlier for a user, conversation or message, including when it was initiated and when it was processed.
- Get Conversation by Id
Returns a single Dixa conversation by its id, including its channel, state, assignment, queue and custom attributes.
- Get Conversation Rating
Returns the latest rating statuses and scores for a conversation, with one entry for each question of the survey.
- Get Conversation Tags
Returns the tags applied to a conversation, including each tag's name, color and state.
- Get Messages in Conversation
Returns all messages in a Dixa conversation, sorted from oldest to newest.
- Get Queue by Id
Returns a Dixa queue by its id, including its name, offering settings, thresholds and the channels that use it. An error occurs if the queue is not found.
- Get User by Id
Returns one Dixa end user (contact) by id, including their name, email addresses, phone numbers, external id and custom attribute values.
- Remove Tag From Conversation
Removes a tag from a Dixa conversation. Active and inactive tags can both be removed.
- Search Conversation
Returns the conversations that contain the specified text, match the specified filters, or both, with snippets showing where the text was found.
- Search Conversations by User
Returns the conversations requested by a specific end user.
- Search Enduser by External ID
Returns the end users whose external ID matches the value you provide.
- Search User by Email Address
Returns the Dixa end users whose email address matches the one you provide.
- Search User by Phone Number
Returns the Dixa end users whose phone number matches the one you specify.
- Set Custom Contact Attributes
Sets custom attribute values on an end user in Dixa and returns the attributes that were updated.
- Set Custom Conversation Attributes
Sets the values of custom attributes on a conversation and returns the conversation's updated custom attributes.
- Tag Conversation
Adds an existing active tag to a conversation.
- Transfer Conversation to Queue
Transfers a conversation to the queue you choose, optionally on behalf of a specific agent, admin or AI agent.
- Update End User
Updates an end user's name, contact details, avatar, external ID and custom contact attributes in Dixa. Only the fields you fill in are changed.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Azure Service Bus
Azure Service Bus to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Azure Service Bus to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Azure Service Bus to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Azure Service Bus to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Azure Service Bus to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Azure Service Bus to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Dixa
Questions
Azure Service Bus and Dixa, 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 Dixa when something happens in Azure Service Bus?
Any of Dixa's 24 actions, including Create Callback Request, Create Conversation, Create User and Update End User. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Dixa to Azure Service Bus?
Dixa has no triggers in the catalog today, so automations start in Azure Service Bus. If you need the other direction, ask: your agent reads Dixa's API documentation and adds it.
Do I have to build a connector for Azure Service Bus or Dixa?
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 Dixa 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.