Call the REST API from a Flow HTTP callout or Apex, and point delivery and inbound webhooks at an endpoint that updates the record.
Plug into the tools your team already runs.
BroadNet connects to the CRM, helpdesk, storefront and marketing stack you already use through the REST API, SMPP and delivery webhooks. Pick a tile, ask for the setup guide, and send your first test message once access is approved.
- 21
- Tools covered
- 7
- Categories
- 8
- API channels
- 329
- API endpoints

One API. Every tool your team already runs.
REST, SMPP and webhooks — the same open surface behind every tool on this page, so BroadNet connects to the CRM, helpdesk, storefront and automation stack you already use.
Five places to start.
Each one connects through the REST API and webhooks. Ask us for the setup guide.
- #1ZapierWebhooks by Zapier + REST APIAsk for the setup guide
- #2SalesforceFlow or Apex HTTP calloutsAsk for the setup guide
- #3ShopifyOrder and fulfilment webhooksAsk for the setup guide
- #4HubSpotWorkflow webhook actionsAsk for the setup guide
- #5ZendeskTrigger webhooks + inbound repliesAsk for the setup guide
Every tool, grouped by where it lives in your stack.
CRM
Send from contact, deal and lifecycle workflows with an HTTP call to the REST API. Replies and delivery receipts come back to your webhook endpoint.
Send from a workflow webhook action to the REST API; your webhook handler logs replies and delivery receipts back to the contact.
Call the REST API with invokeurl from a Deluge custom function in any workflow rule.
Helpdesk
Route inbound SMS and WhatsApp replies into the agent workspace through webhooks, and answer through the REST API.
Point a Zendesk trigger webhook at the REST API to send; add inbound replies to tickets from your inbound-message webhook handler.
Send from your backend on Intercom events via the REST API; post inbound replies into conversations with Intercom's API.
Call the send API from a Freshdesk automation webhook; create tickets from inbound replies in your webhook handler.
E-commerce
Order confirmations, shipping notifications and abandoned-cart recovery, triggered by your store's checkout and fulfilment webhooks.
Subscribe to Shopify order and fulfilment webhooks and call the REST API from your handler.
Call the REST API from a Magento 2 observer on order and shipment events.
Call the REST API from a WooCommerce order-status hook for order, shipping and OTP messages.
Marketing
Trigger SMS and WhatsApp from campaign and CDP events through webhooks and the REST API.
When a Mailchimp audience webhook fires, your backend calls the REST API to send the SMS.
Use a webhook action in a Klaviyo flow to call the REST API with the event data.
Forward tracked events from a Segment Function or webhook destination to the REST API.
Workflow & automation
Use the generic HTTP and webhook modules these tools already ship. No BroadNet-specific app is needed.
Use Webhooks by Zapier: a POST action calls the REST API and a Catch Hook trigger receives delivery receipts and replies.
Use Make's HTTP module to call the REST API and a Custom webhook to receive delivery receipts and replies.
Use n8n's HTTP Request node with the REST API. Your automations can run inside your own VPC.
There is no Python SDK: generate a client from the OpenAPI spec, then receive DLR and MO webhooks in a FastAPI route.
No-code builders
Call the REST API from the builder's API connector and receive delivery and inbound webhooks.
Call the REST API from Bubble's API Connector and receive delivery and inbound webhooks in a backend workflow.
Send form submissions to your backend or an automation webhook, then call the REST API for OTP, lead alerts and confirmations.
Open standards
When you want to talk to the platform directly. Long-lived protocols, full docs, an official TypeScript SDK.
Direct SMPP 3.4 binds with windowing, throttling and delivery receipts. Bind details and throughput are agreed per account.
JSON over HTTPS at api.broadnet.me. Bearer-token auth and an OpenAPI 3.1 spec.
Connect AI agents and assistants to BroadNet over the Model Context Protocol at mcp.broadnet.me/mcp, with the same Bearer token.
Same platform, whichever door you come in.
Whether you call the API from your CRM, wire a no-code scenario or bind over SMPP, you get the same delivery receipts, the same webhooks and the same compliance surface. The matrix below shows how those capabilities map across each route.
| Capability | Business apps (API + webhooks) | Workflow / no-code (HTTP modules) | Open standards (API / SMPP) |
|---|---|---|---|
| Outbound send (SMS / WhatsApp) | Yes | Yes | Yes |
| Two-way inbound replies | Yes | Yes | Yes |
| Delivery receipts (DLR) | Yes | Yes | Yes |
| Retry + reconcile (message ID) | Your logic | Via API step | Yes |
| Bearer-token auth | Yes | Yes | Yes |
| Consent / opt-out handling | Your logic | Your logic | Your logic |
| Runs in your own VPC | — | n8n only | Yes |
| Throughput | Plan-based | Plan-based | Plan-based |
Throughput and specific capabilities vary by plan and destination. See the developer docs for the authoritative API and SMPP reference.
Don’t see your tool? Build it on the API.
Every tool on this page connects through the same REST and SMPP surface that comes with your account: Bearer-token auth, delivery webhooks, an OpenAPI 3.1 spec and an official TypeScript SDK.
# Send your first message — the same call behind every tool on this page.
curl -X POST https://api.broadnet.me/sms/sendSms \
-H "Authorization: Bearer $BROADNET_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"senderId": "BroadNet",
"destinationNumber": "447700900123",
"message": "Your order #4181 has shipped.",
"messageType": "TEXT"
}'
# → 200 OK · the response body is the message IDConnect your first tool.
Request test access, get your API token, connect your tool — and watch the first DLR land on your webhook.