Connect Zapier or Make

Fire a webhook to your automation platform whenever a chat event happens. Use it to log to Sheets, ping Slack, kick off a campaign — anything Zapier or Make can do.

No SetuChat-side code required

Both Zapier and Make have native "Webhook" triggers. Paste their URL into our /connect form, pick events, done. We POST a JSON body to that URL when the event fires.

Step-by-step

Create a webhook trigger on Zapier or Make
Zapier: create a Zap → choose Webhooks by Zapier as trigger → Catch Hook → continue. Zapier shows a Custom Webhook URL like https://hooks.zapier.com/hooks/catch/123/abc/. Copy it.
Make.com: create a scenario → add a Webhooks module → Custom webhook → Add → copy the URL.
Paste the URL into SetuChat
Open setuchat.ai/connect, scroll to Zapier / Make, click Add a webhook. Paste the URL, tick the events you want, save.
Trigger a test event
Send yourself a test message on Messenger / WhatsApp / Instagram / your widget. Within a few seconds, your Zap or Scenario receives the webhook. Use that to map fields.

Events you can subscribe to

• message_received — a customer sent your bot a message. Useful for logging all inbound to a Google Sheet or Notion DB.
• message_sent — the bot replied. Useful for piping high-confidence answers into your CRM or analytics.
• needs_human— a thread the bot couldn't answer confidently. Useful for pinging a Slack channel so a human picks it up fast.

Webhook payload shape

json

{
  "event": "needs_human",
  "tenantId": "...",
  "tenantName": "Your Shop",
  "firedAt": "2026-05-10T03:14:15.000Z",
  "data": {
    "channel": "messenger",
    "peerId": "1234567890",
    "conversationId": 42,
    "trigger": "low_confidence"
  }
}

Best-effort delivery

We try once and retry once on 5xx, then drop. Vendor-side queueing (Zapier's built-in replay, Make's scenario history) is the right place for retry logic — we keep the chat reply path fast and never let webhook latency back up real customer messages.

Security

• The webhook URL itself is the auth — Zapier/Make use unguessable URLs as bearer tokens.
• We encrypt the URL at rest before storing it on your tenant.
• Any POST to a wrong URL is dropped on your platform's side.
• Rotate by clicking Update webhook on /connect — the old URL stops being called immediately.