← Learning Center العربية

Automation & CRM Professional & Enterprise

Connect Thikaa to n8n, Make.com, Zapier or any CRM using the Messaging REST API and signed webhooks. Receive messages from WhatsApp, Instagram, Messenger, Telegram and TikTok inside your workflows — and send replies back — with no custom server.

How it works 1. Get your key 2. Receive (webhook) 3. Send (REST) n8n Make.com Zapier CRM

⚙️ How it works

Thikaa exposes every connected channel through one simple REST API plus signed webhooks. Any tool that can call an HTTP URL can talk to it — so you plug Thikaa into your automations exactly like any other app:

Works with: n8nMake.comZapier HubSpotSalesforceGoogle Sheets any HTTP tool

Full endpoint reference: API documentation →

🔑 Step 1 — Get your API key

  1. In your dashboard open Bot Hub → Messaging API.
  2. Click Create API key, choose the channels it may use, and save.
  3. Copy the key — it starts with tk_live_ and is shown once. Keep it secret.

Your base URL (contains your store id):

https://thikaa.com/<your-store>/api/messaging/
Available on Professional & Enterprise plans. Outbound messages use your normal Thikaa credit.

📥 Step 2 — Receive messages (webhook)

On your key in the Messaging API page, set an HTTPS webhook URL (your n8n / Make / Zapier catch URL). Every incoming customer message is POSTed to it as JSON:

POST <your webhook URL>
X-Thikaa-Event: message.received
X-Thikaa-Signature: sha256=<hmac>

{
  "event": "message.received",
  "instance_id": "inst_xxx",
  "timestamp": "2026-07-17T12:00:00Z",
  "data": {
    "channel": "wd",
    "conversation_id": 12345,
    "message_id": 67890,
    "from": "+201234567890",
    "text": "Hello, is this available?",
    "attachments": []
  }
}

Verify the signature (recommended)

Each request is signed with your key's signing secret. Compute HMAC-SHA256(raw_body, secret) and compare to the X-Thikaa-Signature header to confirm it really came from Thikaa.

Respond with HTTP 200 quickly (within ~2s). Do heavy work asynchronously — slow endpoints may be dropped.

📤 Step 3 — Send messages (REST)

From your workflow, POST to the send endpoint with your key as a Bearer token:

curl -X POST "https://thikaa.com/<your-store>/api/messaging/?action=send" \
  -H "Authorization: Bearer tk_live_xxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{
    "channel": "wd",
    "to": "+201234567890",
    "message": "Thanks! Yes it is in stock ✅"
  }'
Only WhatsApp Direct can start a brand-new conversation with a number. On Telegram, Messenger, Instagram and TikTok the customer must message you first (otherwise HTTP 409).

🔗 n8n

  1. Receive: add a Webhook node (method POST). Copy its Production URL and paste it as the webhook URL on your Thikaa key.
  2. (Optional) add a Crypto node → HMAC SHA256 over {{$json.body}} with your signing secret, and an IF node comparing it to the signature header.
  3. Send: add an HTTP Request node → POST to .../api/messaging/?action=send, Header Auth Authorization: Bearer tk_live_..., JSON body {channel,to,message}.

🔗 Make.com

  1. Receive: add a Webhooks → Custom webhook module, copy its address, and set it as the webhook URL on your Thikaa key.
  2. Send: add an HTTP → Make a request module → POST to the send endpoint, add header Authorization: Bearer tk_live_..., body type Raw / JSON with {channel,to,message}.

🔗 Zapier

  1. Receive: trigger Webhooks by Zapier → Catch Hook. Copy the hook URL into your Thikaa key.
  2. Send: action Webhooks by Zapier → POST to the send endpoint, with header Authorization: Bearer tk_live_... and JSON payload {channel,to,message}.

🗂️ Any CRM (HubSpot, Salesforce, Sheets…)

Combine the two directions to sync Thikaa with your CRM through n8n / Make / Zapier:

Tip: keep the customer's phone number as the shared key between Thikaa and your CRM so records always match.

🚀 Start

Create your first key in Bot Hub → Messaging API, then follow the recipe for your tool above. Need a hand? Message us on WhatsApp from the site.

Start a free 7-day trial →  ·  Full API reference →