---
title: "Connect Azure Service Bus and SendPulse - APIANT.ai"
description: "When \"New Message in Queue\" fires in Azure Service Bus, your agent runs \"Unsubscribe User\" in SendPulse."
canonical: "https://apiant.ai/connect/azure-service-bus-to-sendpulse"
---

# Connect Azure Service Bus and SendPulse

When **New Message in Queue** fires in [Azure Service Bus](https://apiant.ai/connections/azure-service-bus), your agent runs **Unsubscribe User** in [SendPulse](https://apiant.ai/connections/sendpulse), or **New Subscriber** in SendPulse 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 SendPulse **1** trigger SendPulse **9** 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 SendPulse 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 SendPulse can do together

### From Azure Service Bus to SendPulse

- When **New Message in Queue** in Azure Service Bus then **Unsubscribe User** in SendPulse
- When **New Message in Queue** in Azure Service Bus then **Add Subscriber** in SendPulse

### From SendPulse to Azure Service Bus

- When **New Subscriber** in SendPulse then **Send Message to Queue** in Azure Service Bus
- When **New Subscriber** in SendPulse 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 SendPulse

## Triggers and actions 2 triggers · 18 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 Subscriber**

Triggers when a new subscriber is created.

- Action

**Add Subscriber**

Adds a subscriber (email address, with optional variables and tags) to a SendPulse mailing list, with single or double opt-in.

- Action

**Change Variable for Subscriber**

Updates one or more variable values for a subscriber in a SendPulse mailing list.

- Action

**Create Webhook**

Creates an Email service webhook that sends the chosen events to a URL. SendPulse creates one webhook per event.

- Action

**Delete Contact**

Removes a contact's email address from a SendPulse mailing list.

- Action

**Get Subscriber**

Fetches one subscriber of a mailing list by email address, including their status and variables. An error occurs if the email is not in the list.

- Action

**List Mailing Lists**

Returns the mailing lists (address books) in the SendPulse account.

- Action

**List Webhooks**

Returns the Email service webhooks registered on the account, optionally only those for one event.

- Action

**Unsubscribe User**

Marks a contact as unsubscribed in a SendPulse mailing list without deleting it.

- Action

**Update Subscriber**

Updates the variable values (such as name, phone or city) of an existing subscriber in a SendPulse mailing list.

## 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)
- [ **SendPulse** SendPulse is an Integrated messaging platform providing user communication on all devices with Emails, SMS...](https://apiant.ai/connections/sendpulse)

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 SendPulse

- [ **MailUp to SendPulse** MailUp is your complete email delivery solution.](https://apiant.ai/connect/mailup-to-sendpulse)
- [ **HubSpot to SendPulse** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-sendpulse)
- [ **Salesforce to SendPulse** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-sendpulse)
- [ **Google Sheets to SendPulse** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-sendpulse)
- [ **Gmail to SendPulse** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-sendpulse)
- [ **Google Calendar to SendPulse** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-sendpulse)

Questions

## Azure Service Bus and SendPulse, 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 SendPulse when something happens in Azure Service Bus?

Any of SendPulse's 9 actions, including Create Webhook, Update Subscriber, Add Subscriber and Change Variable for Subscriber. Your agent maps the data both ways and tests every scenario before it ships.

###

### Can it also run from SendPulse to Azure Service Bus?

Yes. When something happens in SendPulse, your agent can act in Azure Service Bus too. This page covers both directions: SendPulse'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 SendPulse?

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 SendPulse 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.
