---
title: "Make and Zapier with webhooks"
description: "Send messages from Make scenarios and Zaps with an HTTP request to the REST API, and get delivery statuses and inbound messages via a Make or Zapier webhook."
canonical: "https://omnichannels.ai/developers/zapier-make-webhooks/"
language: "en"
updated: "2026-10-10"
publisher: "BroadNet Technologies"
brand: "OmniChannels.ai"
section: "Tools"
---

# Make and Zapier with webhooks

Canonical: https://omnichannels.ai/developers/zapier-make-webhooks/
Language: en
Publisher: OmniChannels.ai by BroadNet Technologies

There is no dedicated OmniChannels.ai app in Make or Zapier. Both tools still work with the API through their generic building blocks:

- **Send:** an HTTP request to the REST API with your Bearer token.
- **Receive:** a webhook URL from Make or Zapier, configured as the webhook on your account, so delivery statuses and inbound messages start a scenario or Zap.

The examples use `POST /sms/sendSms`. Every other channel works the same way; take the path and fields from the channel's page or the [OpenAPI spec](/developers/openapi/). For AI agents that call the messaging tools themselves, see the [MCP server](/developers/mcp/) instead.

## Before you start

- An API token for your account (see [Authentication](/developers/authentication/)). Use test credentials, which send only to your own verified numbers, until the automation works.
- A sender ID that is approved for your destination country (see the [SMS API](/developers/sms/) page).

Store the token in the tool's connection or credential settings where it offers them, not typed into a step that other people can see or copy.

## Send from Make

Make's HTTP app sends any request. Add an **HTTP → Make a request** module and fill it in:

| Field | Value |
| --- | --- |
| URL | `https://api.broadnet.me/sms/sendSms` |
| Method | `POST` |
| Authentication type | **API key**, with a keychain that sends `Bearer <your token>` in the `Authorization` header. Make recommends a keychain over typing credentials into the Headers field. |
| Body content type | `application/json`, entered as a JSON string |

```json title="Body"
{
  "senderId": "OmniDemo",
  "destinationNumber": "447700900123",
  "message": "Your appointment is confirmed for 3 pm.",
  "messageType": "TEXT"
}
```

Map the number and text from earlier modules into the body. The response is the message ID: store it (in a data store, sheet or CRM record) so you can match delivery statuses to the message later. Make's [HTTP app documentation](https://apps.make.com/http) describes the module's fields and authentication options.

## Send from Zapier

Add a **Webhooks by Zapier** action and choose **POST** (or **Custom Request** if you need full control over the body):

| Field | Value |
| --- | --- |
| URL | `https://api.broadnet.me/sms/sendSms` |
| Payload type | JSON |
| Data | `senderId`, `destinationNumber`, `message`, `messageType` |
| Headers | `Authorization`: `Bearer <your token>` |

Webhooks by Zapier is not available on Zapier's Free plan; see [Zapier's webhook documentation](https://help.zapier.com/hc/en-us/articles/8496288690317-Trigger-Zaps-from-webhooks) for plan details.

## Receive delivery statuses and inbound messages

The platform pushes delivery statuses and inbound messages to the webhook URL configured on your account. Point it at Make or Zapier:

1. **Make:** add a **Webhooks → Custom webhook** trigger to a new scenario, create the webhook and copy its address. **Zapier:** add a **Webhooks by Zapier** trigger with the **Catch Hook** event and copy the URL from the trigger's test step.
2. Send the URL to our team or your account admin to configure it on your account (resellers can set one per sub-account). See [Webhooks](/developers/webhooks/#set-up-your-endpoint).
3. Send a test message to your own number so a real event arrives, then let Make determine the data structure or run Zapier's **Test trigger** to load the fields.
4. Add the steps that use the event, for example updating the message's status in your CRM.

Keep these rules from the [Webhooks](/developers/webhooks/) guide:

- **Payload fields vary by channel.** Build the scenario or Zap from a real event from your account, not from an assumed field list.
- **Statuses can repeat and arrive out of order.** A late `SENT` must not overwrite a `DELIVERED` you already stored.
- **Never send again from the webhook flow.** A failed status should alert a person or a separate process, not trigger an automatic resend.
- **Know the tool's limits.** Make queues incoming webhook requests and answers `429` when its rate limit is exceeded, and deactivates a webhook that is not connected to a scenario for more than five days. Check [Make's webhook documentation](https://help.make.com/webhooks) and Zapier's plan limits before you route high volumes through them.

For high message volumes, or when every status must be processed, receive webhooks on your own endpoint and pass a summary to Make or Zapier instead.

## Next steps

- [Webhooks and delivery statuses](/developers/webhooks/): status meanings and handler rules.
- [Use the MCP server with n8n](/developers/mcp-n8n/): the same pattern in n8n, plus AI Agent tools.
- [Errors and limits](/developers/errors-and-limits/): which errors to retry.