Overview
This node allows sending messages to an Azure Service Bus queue or topic. It is designed for scenarios where you want to integrate n8n workflows with Azure's messaging infrastructure, enabling asynchronous communication between distributed systems or components.
Typical use cases include:
- Sending event notifications or commands from n8n workflows to other applications listening on Azure Service Bus.
- Integrating with microservices architectures that rely on message queues or topics for decoupled communication.
- Offloading processing tasks by pushing messages to a queue for later consumption.
For example, you could use this node to send JSON-formatted data representing an order or user action to an Azure Service Bus queue, which another service then processes asynchronously.
Properties
| Name | Meaning |
|---|---|
| Data | The message content to send, provided as a JSON-formatted string. This is the payload that will be sent to the Azure Service Bus. |
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 and contains the original JSON data. If an error occurs during sending 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 name (queue or topic) to connect and send messages.
- Needs appropriate credentials configured in n8n to authenticate with Azure Service Bus.
- Uses the official Azure Service Bus SDK (
@azure/service-bus) for sending messages. - The node expects the connection string and entity path to be combined properly to create the client.
Troubleshooting
Common issues:
- Incorrect or missing Azure Service Bus connection string or entity name will cause authentication or connection failures.
- Malformed JSON in the "Data" property can lead to unexpected message content or errors.
- Network connectivity problems may prevent messages from being sent.
Error messages:
- Errors thrown by the Azure SDK will be surfaced. If "Continue On Fail" is disabled, the node execution stops on the first error.
- When enabled, errors are attached to the corresponding output item under an
errorproperty for easier debugging.
Resolution tips:
- Verify that the Azure Service Bus connection string and entity name are correct and have sufficient permissions.
- Ensure the "Data" input is valid JSON or properly formatted string.
- Check network access to Azure endpoints.