Azure Message Bus Node

Sends and receives messages from Azure Service Bus

Actions2

- Send
- Receive

Overview

This node integrates with Azure Service Bus to send or receive messages from queues or topics. It is useful in scenarios where you need reliable messaging between distributed applications or services, such as decoupling microservices, implementing event-driven architectures, or processing asynchronous workflows.

Send operation: Sends a JSON message to a specified queue or topic.
Receive operation: Retrieves messages from a queue or subscription of a topic, with options to control how messages are processed after retrieval (complete, abandon, dead-letter) and whether to peek or actually receive messages.

Practical examples:

Sending an order payload to a queue for downstream processing.
Receiving notifications from a topic subscription and automatically marking them as completed.
Peeking at messages in a queue without removing them to monitor traffic.

Properties

Name	Meaning
Connection String	Connection string used to authenticate with Azure Service Bus.
Queue or Topic Name	The name of the queue or topic in Azure Service Bus where messages will be sent or received.
Subscription Name (Se for Tópico)	The subscription name if using a topic; leave empty if using a queue.
Message Body (JSON)	The content of the message to send, formatted as JSON. (Only for Send operation)

Output

The node outputs a single item with a json field containing:

For Send operation:

{
  "success": true,
  "operation": "send",
  "queueOrTopic": "<name>",
  "subscriptionName": "<subscription or empty>",
  "messageSent": <the JSON message body sent>
}

For Receive operation:

{
  "success": true,
  "operation": "receive",
  "queueOrTopic": "<name>",
  "subscriptionName": "<subscription or empty>",
  "messagesReceived": [<array of message bodies>]
}

No binary data output is produced by this node.

Dependencies

Requires an active Azure Service Bus namespace with appropriate queues or topics configured.
Needs a valid connection string credential for Azure Service Bus authentication.
Uses the official Azure SDK package for Service Bus (@azure/service-bus).

Troubleshooting

Common issues:
- Invalid or expired connection string causing authentication failures.
- Incorrect queue/topic or subscription names leading to resource not found errors.
- Permissions missing on the Service Bus namespace for sending or receiving messages.
- Network connectivity problems preventing access to Azure Service Bus endpoints.
Error messages:
- Errors during execution are wrapped with a message like:
  Erro ao executar a operação 'send': <error details> or
  Erro ao executar a operação 'receive': <error details>
- To resolve, verify the connection string, resource names, and network access.
- Ensure the subscription name is provided only when working with topics.
- For receive operations, check that the post-processing action matches your intended message handling.