Send message
Send a text message with a stable ID; acceptance does not confirm processing.
Connector library
Azure Service Bus connector.
Send text messages, receive and lock one queued message, complete successful processing or abandon a lock through four Azure Service Bus REST actions.
Connector download
Download Azure Service Bus
Versioned ZIP for your CXFabric tenant.
Use this connector in a flow
- Register the ZIP in your tenant, or add a new version if the connector is already installed.
- Create or select a credential if the action requires one.
- In a Draft flow, add an available action, choose its version, connect it, and map inputs.
- Test the step and flow; review output and failures before activation.
See readme.md in the ZIP for settings and limitations.
- Version
v0.2.0.0 Choose version
- Release
- 2026-10-03
- Package
- Implemented source
- Schema credentials
- Bearer token
- Connection settings
- Namespace Name, Queue Name
- Package size
- 8 KB
- SHA-256
9777ad74e6c968c056917e7e0c31511c427785df4eda0c790c4663d52e030559
Version history
What's new
- v0.2.0.0Latest · 2026-10-03 · Implemented source
Send text messages, receive and lock one queued message, complete successful processing or abandon a lock through four Azure Service Bus REST actions.
- v0.1.1.0Earlier · 2026-10-02 · Starter scaffold
Historical configurable HTTP scaffold.
Included in this version
Included actions
Implemented in v0.2.0.0. Use a separate flow trigger; no webhook trigger is included.
Peek lock message
Receive and lock one message; an empty wait does not establish queue exhaustion.
Complete message
Complete/delete one previously locked message after successful processing.
Abandon message
Release a previously received message lock for another processing attempt.
Vendor API
API and access
Implementation considerations
- For broad cloud and database APIs, CXFabric starts with get/list/create/update/delete plus query, publish, and upload/download patterns.
- Confirm networking, private endpoints, credentials, IAM scopes, region, batching limits, and customer-owned runtime access.
- Keep object keys, message IDs, query IDs, and run IDs visible for retries and support.
- Select a Microsoft Entra bearer token for Service Bus with the required Data Sender or Data Receiver role.
- Peek-lock changes broker state. Process the message before confirmed completion; use the exact same-queue lock URL for settlement.
Related connectors
More in Data, Storage & Cloud APIs
Support
Need help with Azure Service Bus?
Tell us what you need to connect or change.