Connect WhatsApp and marketing tools

How it works

AlliDesk does not hold a WhatsApp account of its own. Your WhatsApp tool already has your number, your approved templates and your flows. You give AlliDesk the tool's webhook URL; when an event you picked happens, AlliDesk sends it there as JSON within seconds, and the tool's flow sends the message.

1. In your tool, add a webhook trigger to a flow, journey or workflow, and copy the URL (and token, if it shows one).
2. In AlliDesk open Settings → Integrations → WhatsApp & marketing tools, press Connect beside your tool, paste it, tick the events and Save.
3. Press Send test event with your own number. Your tool shows what arrived; map phone, name and the fields under data into your template.
4. Switch the flow on in your tool. Every delivery shows under Recent deliveries in AlliDesk, with the tool's answer.

You can connect up to ten tools, and one tool more than once — for example one Spur flow for loyalty and another for returns. Only a store owner can connect, change or remove a tool.

Spur

Start a Spur WhatsApp flow from any AlliDesk event.

1. In Spur open Automations → Automation Flows → Create New Flow.
2. Pick WhatsApp as the channel and Webhook as the trigger. Spur shows the flow's webhook URL — copy it.
3. In AlliDesk open Settings → Integrations → WhatsApp & marketing tools, press Connect beside Spur, and paste it, tick the events you want, and Save.
4. Press Send test event — the tool now has a sample to map.
5. Back in Spur press Test Webhook → Check for Received Requests. Map phone and name, then use fields such as {{trigger.data.points}} in your template.

Spur's own guide

BIK

Trigger a BIK journey on WhatsApp from any AlliDesk event.

1. In BIK open the Journey Builder and start a journey on the WhatsApp channel with Webhook as the trigger.
2. Copy the webhook URL BIK generates for that journey.
3. In AlliDesk open Settings → Integrations → WhatsApp & marketing tools, press Connect beside BIK, and paste it, tick the events you want, and Save.
4. Press Send test event — the tool now has a sample to map.
5. In BIK map phone number and email as the unique IDs, then pick the other fields from the variable picker.

BIK's own guide

Interakt

Every event lands on the customer's Interakt profile, ready for campaigns.

1. In Interakt open Settings → Developer Setting and copy the Secret Key.
2. In AlliDesk open Settings → Integrations → WhatsApp & marketing tools, press Connect beside Interakt, and paste it as it is — Interakt already encodes it — tick the events, and Save.
3. Press Send test event, then open that customer in Interakt: the event (for example “Points earned”) shows with its details as traits.
4. Use those events when you build campaigns in Interakt.

Interakt's own guide

WATI through Pabbly Connect

Send a WATI template for any event, through a Pabbly Connect workflow.

1. In Pabbly Connect create a workflow with Webhook by Pabbly as the trigger and copy its webhook URL.
2. In AlliDesk open Settings → Integrations → WhatsApp & marketing tools, press Connect beside WATI, and paste it, tick the events you want, and Save.
3. Press Send test event so Pabbly captures a sample.
4. Add the WATI action that sends a template message, and map phone and the event's fields into the template.

WATI's own guide

AiSensy through Pabbly Connect

Send an AiSensy template for any event, through a Pabbly Connect workflow.

1. In Pabbly Connect create a workflow with Webhook by Pabbly as the trigger and copy its webhook URL.
2. In AlliDesk open Settings → Integrations → WhatsApp & marketing tools, press Connect beside AiSensy, and paste it, tick the events you want, and Save.
3. Press Send test event so Pabbly captures a sample.
4. Add the WhatsApp by AiSensy action that sends a template message, and map phone and the event's fields.

AiSensy's own guide

Pabbly Connect

Catch events in Pabbly and pass them to any app it connects.

1. In Pabbly Connect create a workflow with Webhook by Pabbly as the trigger and copy its webhook URL.
2. In AlliDesk open Settings → Integrations → WhatsApp & marketing tools, press Connect beside Pabbly Connect, and paste it, tick the events you want, and Save.
3. Press Send test event so Pabbly captures a sample, then add the actions you want.

Pabbly Connect's own guide

Zapier

Start a Zap from any event and reach WATI, Zoko or thousands of apps.

1. In Zapier create a Zap with Webhooks by Zapier → Catch Hook as the trigger and copy the webhook URL. Webhooks by Zapier needs a paid Zapier plan.
2. In AlliDesk open Settings → Integrations → WhatsApp & marketing tools, press Connect beside Zapier, and paste it, tick the events you want, and Save.
3. Press Send test event, then in Zapier test the trigger to pull in the sample and add your action.

Zapier's own guide

Make

Run a Make scenario from any event.

1. In Make start a scenario with Webhooks → Custom webhook, add a webhook and copy its address.
2. In AlliDesk open Settings → Integrations → WhatsApp & marketing tools, press Connect beside Make, and paste it, tick the events you want, and Save.
3. Press Send test event while Make is listening, so it learns the data structure.

Make's own guide

n8n

Start an n8n workflow from any event.

1. In n8n add a Webhook node, set the method to POST, and copy the Production URL.
2. If you set Header Auth on the node, put the same header name and value in Token below.
3. In AlliDesk open Settings → Integrations → WhatsApp & marketing tools, press Connect beside n8n, and paste it, tick the events you want, and Save.
4. Activate the workflow, then press Send test event.

n8n's own guide

Custom webhook

Any other WhatsApp tool, CRM or server that gives you a webhook URL.

1. In your tool, create an incoming webhook (it may be called a webhook trigger or API trigger) and copy its URL and token.
2. In AlliDesk open Settings → Integrations → WhatsApp & marketing tools, press Connect beside Custom webhook, and paste the URL, and the token with the header your tool expects. Most use Authorization: Bearer.
3. Tick the events, Save, and press Send test event to see exactly what arrives.
4. Map phone, name and the fields under data into your message. Every request is signed, so your server can check it came from AlliDesk.

What AlliDesk sends

One POST per event, per person, per connection, with Content-Type: application/json. Only HTTPS URLs on the public internet are accepted.

{
  "event": "loyalty.points_earned",
  "event_name": "Points earned",
  "event_id": "cmh3w2k0p0004",
  "occurred_at": "2026-09-17T10:42:07.000Z",
  "test": false,
  "audience": "customer",
  "phone": "919876543210",
  "phone_national": "9876543210",
  "country_code": "91",
  "name": "Asha Verma",
  "first_name": "Asha",
  "email": "asha@example.com",
  "store": {
    "name": "Your store",
    "domain": "yourstore.in",
    "currency": "INR"
  },
  "data": {
    "first_name": "Asha",
    "points": "120",
    "points_name": "points",
    "reason": "a product review",
    "balance": "820",
    "account_url": "https://yourstore.in/apps/account"
  }
}

{
  "phoneNumber": "9876543210",
  "countryCode": "+91",
  "event": "Points earned",
  "traits": {
    "first_name": "Asha",
    "points": "120",
    "points_name": "points",
    "reason": "a product review",
    "balance": "820",
    "account_url": "https://yourstore.in/apps/account",
    "allidesk_event": "loyalty.points_earned",
    "allidesk_event_id": "cmh3w2k0p0004",
    "store_name": "Your store",
    "email": "asha@example.com"
  }
}

Every event (44)

Tick any of these on a connection. A new event AlliDesk adds appears here and on the settings page.

Who an event is about

• A customer event carries that customer's phone, name and email, from their account on your store.
• A store alert (low stock, a new return, a low-rated review, a COD order unconfirmed) goes once for each phone number in Alerts → Recipients, or else once for each of your Team WhatsApp numbers on the settings page.
• A customer who answered no to “Send order updates by SMS or WhatsApp” on their account gets nothing through your tools; the delivery shows as Skipped. A sign-in code they asked for is the exception.
• Spur, BIK, Interakt, WATI and AiSensy need a phone, so an event with no number is skipped for them.
• The Sign-in code event carries the code itself: tick it only on a tool that sends it straight to the customer.

Checking the signature

Tools like Spur and Zapier do not need this. If the URL is your own server, check each request came from AlliDesk: copy the signing secret from the connection's Advanced section, then compare signatures on the raw body.

import { createHmac, timingSafeEqual } from "node:crypto";

// Express: app.post("/allidesk", express.raw({ type: "application/json" }), handler)
export function fromAllidesk(rawBody, headers, signingSecret) {
  const timestamp = headers["x-allidesk-timestamp"];
  const received = String(headers["x-allidesk-signature"] ?? "").replace(/^sha256=/, "");
  // Refuse anything older than five minutes, so a copied request cannot be replayed.
  if (!timestamp || Math.abs(Date.now() / 1000 - Number(timestamp)) > 300) return false;
  const expected = createHmac("sha256", signingSecret).update(`${timestamp}.${rawBody}`).digest("hex");
  return received.length === expected.length && timingSafeEqual(Buffer.from(received), Buffer.from(expected));
}

Retries and the log

• Any 2xx answer is delivered. Answer quickly — AlliDesk waits 10 seconds by default (3 to 30 in Advanced).
• A 5xx, 408, 429, a timeout or a connection error is tried again up to 5 times in all, after about ½, 1, 2, 4 minutes.
• Other 4xx answers are not retried: they mean the URL or token is wrong. A redirect is not followed — paste the final URL.
• Recent deliveries on the settings page shows each one with the tool's answer, for 30 days. The body is not stored, since it can carry a sign-in code.
• Switching a connection off stops events at once, including retries still waiting.

When nothing arrives

Still stuck? Write to hello@allidesk.com with the connection's name and the time of the delivery.