Make

There are three ways to use Blueticks in Make:

Option 1: the Blueticks app for Make

1. Open the Blueticks app invite link while logged in to Make and install the app in your organization.
2. Create a Blueticks API key (bt_live_…) at app.blueticks.co → Blueticks API — see Authentication.
3. Add any Blueticks module to a scenario and create the connection with your key.

The app covers messages (send, schedule, get, update, cancel, download media), chats and contacts, groups, audiences and campaigns, plus six instant triggers: incoming messages, message status updates, poll votes, group membership changes, campaign events and connection changes. Triggers register a Blueticks webhook when the scenario is turned on and remove it when it is turned off.

Option 2: HTTP module + Custom webhook

You need a Blueticks API key (bt_live_…) — see Authentication.

Send a WhatsApp message (action)

Add an HTTP → Make a request module:

{
  "type": "text",
  "text": "Hi Dana, your order has shipped."
}

The last part of the URL is the recipient: a phone number in international format with a leading +, or a chat id — 15550100123@c.us for a person, …@g.us for a group. Add "sendAt": "2026-11-02T09:00:00Z" to schedule it instead of sending now. A successful call returns 201. Media and polls use the same endpoint with "type": "media" / "type": "poll" — see Sending messages.

Any other endpoint in the API reference works the same way: same Authorization header, JSON body.

React to WhatsApp events (trigger)

1. Start the scenario with Webhooks → Custom webhook, create a new webhook and copy its URL.
2. Subscribe that URL to the Blueticks events you want — once, with any HTTP client (or an HTTP module run once in Make):

curl -X POST https://api.blueticks.co/v1/webhooks \
  -H "Authorization: Bearer bt_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://hook.eu1.make.com/your-webhook-id",
    "events": ["new_message_received_webhook"],
    "description": "Make: incoming WhatsApp"
  }'

3. Trigger the event once (for example, message your WhatsApp number from another phone) so Make learns the data structure. Every event arrives as { "id", "type", "created_at", "data" } — the event's fields are under data.

The response includes a signingSecret for verifying deliveries. Make's webhook URL is already unguessable, so verification is optional here.

Events you can subscribe to (full list in Receiving webhooks):

Option 3: Make's MCP Client

Make's MCP Client app can call any MCP server. Point it at:

https://api.blueticks.co/mcp

and authenticate with OAuth — you'll see the Blueticks consent screen and click Authorize. The MCP server only accepts OAuth tokens; a bt_live_ API key does not work here (use it with Option 1 or 2 instead). The available tools and actions are listed on the Claude page.

Example scenarios

Google Sheets row → send a WhatsApp message

1. Google Sheets → Watch New Rows on a sheet with Phone and Message columns. Store phones in international format, e.g. +15550100123.
2. HTTP → Make a request: URL https://api.blueticks.co/v1/scheduled-messages/{{Phone}}, method POST, header Authorization: Bearer bt_live_…, JSON body {"type": "text", "text": "{{Message}}"} (map the two columns from the trigger).

Incoming WhatsApp → Slack

1. Webhooks → Custom webhook, subscribed to new_message_received_webhook as shown above.
2. Slack → Create a Message in your support channel, mapping the sender and message text from the webhook's data.

Campaign completed → CRM

1. Webhooks → Custom webhook, subscribed to campaign.completed.
2. Your CRM's update record module. The event's data carries the campaign's cmpId, name, audienceId, status, the counters totalCount, sentCount, deliveredCount, readCount, failedCount, and completedAt — map them onto the CRM record.

Troubleshooting

429 Too Many Requests on the free plan. The free plan allows 5 requests per 6-hour window, shared across the REST API and the MCP server — each HTTP module run and each MCP tool call counts once. Windows are fixed in UTC: 00:00–06:00, 06:00–12:00, 12:00–18:00, 18:00–24:00. Wait for the next window, or upgrade: any paid plan is unlimited. Watch out for scenarios that run on a short schedule — they burn the free quota quickly.

"No WhatsApp engine is connected". Blueticks sends through the WhatsApp connection on your account; while it's down, calls that need a live WhatsApp connection fail with 503. Check it with GET /v1/ping — an empty whatsappConnections array means nothing is connected — and reconnect in the Blueticks app. Subscribe a scenario to session.disconnected to get alerted when it drops.

Phone number rejected (400). The recipient must start with + and the country code (+15550100123); bare digits, or numbers starting with 0 / 00, are rejected. Spaces, dashes, dots, and parentheses are stripped. If a tool mangles the + in a URL, use the chat-id form 15550100123@c.us instead.

Webhook stopped firing. After 8 consecutive failed deliveries (for example, the Make scenario was off) the webhook auto-disables. Turn the scenario back on, then re-enable the webhook with PATCH /v1/webhooks/{id} and {"status": "enabled"}.