In short
Make works with OmniChannels.ai through its generic HTTP and Webhooks apps, not a dedicated app. The HTTP Make a request module calls our REST API with your Bearer token to send WhatsApp, SMS and other messages, and a Custom webhook trigger receives delivery statuses and inbound messages configured on your account. Test sends go to your own verified numbers first.
What you can do
Send a WhatsApp template when a new row is added
When a row is added to a sheet, database or Airtable base, send an approved WhatsApp template with the row's values, to contacts who have opted in.
Send order and appointment updates
When a store, booking or CRM module reports a change, send an SMS or WhatsApp update to the customer's number.
Alert the team when a delivery fails
A Custom webhook receives delivery statuses; a filter passes FAILED and REJECTED events to a chat message or ticket instead of resending.
Keep a delivery log
Store each message ID in a data store or sheet, then update its status as events arrive, ignoring late or duplicate events.
Send bulk campaigns from a list
Build a recipient list from earlier modules and send it to a bulk endpoint with a multipart form-data body, which the HTTP module supports.
How it connects
To send, add an HTTP Make a request module with the method POST and the channel's send path on https://api.broadnet.me. Use an API key keychain that sends Bearer and your token in the Authorization header, which Make recommends over typing credentials into the Headers field. Single SMS takes a JSON body; bulk and most other channel sends take multipart form data.
To receive, add a Webhooks Custom webhook trigger to a new scenario, copy its address and send it to our team or your account admin to configure on your account. Send a test message to your own number so Make can determine the data structure from a real event, since payload fields vary by channel.
- Send: HTTP Make a request module, POST to https://api.broadnet.me
- Authentication: API key keychain sending Authorization: Bearer <token>
- Receive: Custom webhook address configured on your account
- Make answers 429 above its webhook rate limit and deactivates unused webhooks
- Never resend automatically from a status scenario
Set it up
- 1
Request API access
Request test access and receive an API token. Test sends go only to your own verified numbers.
Guide: Quickstart: send your first message - 2
Create a keychain
In the HTTP module, create an API key keychain that sends Bearer and your token in the Authorization header.
Guide: Authentication - 3
Add the sending module
Add HTTP Make a request with POST, the channel's send URL and the body fields mapped from earlier modules. Store the returned message ID.
Guide: Make and Zapier with webhooks - 4
Receive delivery statuses
Create a scenario with a Custom webhook trigger and send its address to our team or your account admin.
Guide: Webhooks and delivery statuses - 5
Test with your own number
Send a test message to your verified number and let the webhook determine the data structure from the real event.
Vendor documentation
Make is a trademark of its owner. OmniChannels.ai is not affiliated with or endorsed by Make; this page describes a connection built with Make's own MCP, HTTP or webhook features.
