> For the complete documentation index, see [llms.txt](https://docs.digibee.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digibee.com/documentation/connectors-and-triggers/connectors/azure/servicebus.md).

# Azure ServiceBus

Discover more about the Azure ServiceBus connector and how to use it on the Digibee Integration Platform.

{% hint style="info" %}
The content of this documentation is under revision and may change. We appreciate your understanding as we work to improve it.
{% endhint %}

**Azure ServiceBus** sends and receives messages to/from Azure Event Bus.

## **Parameters**

Take a look at the configuration options for the component. Parameters supported by [Double Braces expressions](/documentation/connectors-and-triggers/double-braces/overview.md) are marked with `(DB)`.

### **General tab**

<table data-full-width="true"><thead><tr><th>Parameter</th><th>Description</th><th>Default value</th><th>Data type</th></tr></thead><tbody><tr><td><strong>Dynamic Account</strong></td><td>When active, the connector will use the account dynamically. Otherwise, it will use the account statically.</td><td>False</td><td>Boolean</td></tr><tr><td><strong>Account Name</strong> <code>(DB)</code></td><td>The name of the dynamic account used by the connector. This account must have been previously configured in a <a href="/documentation/connectors-and-triggers/connectors/tools/store-account.md"><strong>Store Account</strong></a> connector in the pipeline for this process to take effect. It is only available if the <strong>Dynamic Account</strong> parameter is active.</td><td>N/A</td><td>String</td></tr><tr><td><strong>Account</strong></td><td>The account used by the connector. It is only available if the <strong>Dynamic Account</strong> parameter is inactive.</td><td>N/A</td><td>Account</td></tr><tr><td><strong>Service Bus Type</strong></td><td>The ServiceBus type of connection to execute. <strong>Queue</strong> is for a typical queue option and <strong>Topic</strong> for subscription based model.</td><td>Queue</td><td>String</td></tr><tr><td><strong>Fail On Error</strong></td><td>If the option is activated, the pipeline's execution with an error will be interrupted. Otherwise, the pipeline execution proceeds, but the result will show a false value for the <code>"success"</code> property.</td><td>False</td><td>Boolean</td></tr></tbody></table>

### **Optional tab**

<table data-full-width="true"><thead><tr><th>Parameter</th><th>Description</th><th>Default value</th><th>Data type</th></tr></thead><tbody><tr><td><strong>Topic Or Queue Name</strong> <code>(DB)</code></td><td>Selected topic name or the queue name, depending on <strong>Service Bus Type</strong> parameter. For example if the Service Bus Type is Queue, then this will be the queue name and if the Service Bus Type is Topic, this will be the topic name.</td><td>N/A</td><td>String</td></tr><tr><td><strong>Amqp Transport Type</strong></td><td>Sets the transport type by which all the communication with Azure Service Bus occurs. Default value is AmqpTransportType#AMQP.</td><td>AMQP</td><td>String</td></tr><tr><td><strong>Producer Operation</strong></td><td>Sets the desired operation to be used in the producer.</td><td>sendMessages</td><td>String</td></tr><tr><td><strong>Scheduled Enqueue Time</strong> <code>(DB)</code></td><td>Sets OffsetDateTime at which the message should appear in the Service Bus queue or topic.</td><td>N/A</td><td>String</td></tr><tr><td><strong>Body</strong> <code>(DB)</code></td><td>The body, if applicable.</td><td><code>{ }</code></td><td>JSON</td></tr></tbody></table>

### **Headers tab**

<table data-full-width="true"><thead><tr><th>Parameter</th><th>Description</th><th>Default value</th><th>Data type</th></tr></thead><tbody><tr><td><strong>Application Properties</strong> <code>(DB)</code></td><td>The application properties (also known as custom properties) on messages sent and received by the producer and consumer, respectively.</td><td>N/A</td><td>JSON</td></tr><tr><td><strong>Scheduled Enqueue Time</strong> <code>(DB)</code></td><td>Gets the scheduled enqueue time of this message.</td><td>N/A</td><td>String</td></tr><tr><td><strong>Producer Operation</strong></td><td>Overrides the desired operation to be used in the producer.</td><td>N/A</td><td>String</td></tr></tbody></table>

### **Documentation tab**

<table data-full-width="true"><thead><tr><th>Parameter</th><th>Description</th><th>Default value</th><th>Data type</th></tr></thead><tbody><tr><td><strong>Documentation</strong></td><td>Section for documenting any necessary information about the connector configuration and business rules.</td><td>N/A</td><td>String</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.digibee.com/documentation/connectors-and-triggers/connectors/azure/servicebus.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.