Overview
This node sends messages to an Azure Service Bus queue or topic. It is designed to take input data in JSON format, package it as a message, and send it to the specified Azure Message Bus entity. This node is useful for integrating workflows with Azure messaging infrastructure, enabling asynchronous communication between distributed systems or triggering downstream processes.
Common scenarios include:
- Sending event notifications or telemetry data to Azure Service Bus.
- Integrating n8n workflows with other Azure services that consume messages from Service Bus.
- Decoupling microservices by using message queues or topics for communication.
Example: A workflow collects sensor data and uses this node to send each data point as a message to an Azure Service Bus queue for further processing by another system.
Properties
| Name | Meaning |
|---|---|
| Payload | Data in JSON format to be sent as the message body |
Output
The node outputs the original input items enriched with the result of the send operation. The output json field contains the same structure as the input, potentially augmented with response details from the Azure Service Bus SDK indicating the success or failure of sending each message.
If binary data were supported (not indicated here), it would represent any binary content associated with the message, but this node only handles JSON string payloads.
Dependencies
- Requires an Azure Service Bus connection string and entity name (queue or topic) configured via credentials.
- Uses the official Azure Service Bus SDK (
@azure/service-bus) to send messages. - Requires proper permissions on the Azure Service Bus namespace to send messages.
Troubleshooting
Common issues:
- Invalid or missing Azure Service Bus connection string or entity path will cause authentication or connection errors.
- Malformed JSON in the Payload property may lead to unexpected message content or runtime errors.
- Network connectivity problems can prevent messages from being sent.
Error messages:
- Errors thrown by the Azure SDK are wrapped and reported per item. If "Continue On Fail" is disabled, the node execution stops at the first error.
- To resolve credential errors, verify the connection string and entity path are correct and have sufficient permissions.
- For JSON parsing issues, ensure the Payload property contains valid JSON-formatted strings.