Azure Message Bus Node

Basic Azure Message Bus Node

Overview

This node allows sending messages to an Azure Service Bus. It is designed to publish events with associated data onto a specified event bus topic or queue in Azure. This can be useful for integrating workflows with other systems that listen to Azure Service Bus events, enabling asynchronous communication and event-driven architectures.

Typical use cases include:

Sending notifications or commands to other services via Azure Service Bus.
Integrating n8n workflows with Azure-based messaging infrastructure.
Decoupling components by using message queues or topics for event distribution.

For example, you might send an event named "orderCreated" with order details as JSON data, which downstream services can consume asynchronously.

Properties

Name	Meaning
Event Name	The name of the event defined on the Azure event bus to send. This identifies the type of event being published.
Data	The payload data to send with the event, formatted as a JSON string. This contains the actual information related to the event.

Output

The node outputs the same items it receives as input, potentially augmented with the result of the send operation. Each output item corresponds to an input item, preserving the original structure.

The json field contains the original input data.
If an error occurs and the node is configured to continue on failure, the output item will include an error field describing the issue.
No binary data is produced by this node.

Dependencies

Requires an Azure Service Bus connection string and entity path (queue or topic name) provided via credentials.
Uses the official Azure Service Bus SDK (@azure/service-bus) to send messages.
The node expects a valid API authentication token or connection string credential configured in n8n for Azure Service Bus access.

Troubleshooting

Common issues:
- Invalid or missing Azure Service Bus connection string or entity path will cause authentication or connection errors.
- Malformed JSON in the "Data" property may lead to unexpected message content or failures.
- Network connectivity problems to Azure Service Bus endpoints.
Error messages:
- Errors thrown during message sending are caught per item. If "Continue On Fail" is disabled, the node stops execution and reports the error with the item index.
- If enabled, errors are attached to the corresponding output item under an error property.
Resolution tips:
- Verify the correctness of the Azure Service Bus connection string and entity path.
- Ensure the "Data" property contains valid JSON-formatted strings.
- Check network access and firewall settings allowing outbound connections to Azure Service Bus.