Integrations

Connect to Zapier

Send Adoomi events — new leads, escalations, negative feedback, and more — into Slack, Google Sheets, your CRM, and 6,000+ other apps. No code required: Zapier's "Catch Hook" receives our signed webhooks directly.

Before you start. Webhooks are available on every paid plan (Local, Growth, Scale and Advanced), and you'll need a Zapier account. The steps below use Zapier's own Catch Hook, and they work for any paid workspace.

The Adoomi Zapier app (invite only)

Adoomi also has its own Zapier app, with a separate trigger for each of the eight events. It is invite only for now, so it does not show up when you search Zapier's app list. To get an invite, email hello@adoomi.ai. You connect the app with a key from Settings → API keys, on the same paid plans as webhooks. When you switch a Zap on, the app adds its own webhook destination for you.

Step by step

  1. 1

    Create a "Catch Hook" Zap in Zapier

    In Zapier, create a new Zap and choose Webhooks by Zapier as the trigger, then the Catch Hook event. Zapier generates a unique https://hooks.zapier.com/… URL — copy it. Leave the "Pick off a child key" field blank so Zapier receives the whole payload.

  2. 2

    Add the URL as a webhook destination

    In Adoomi, open Settings → Webhooks, add a destination, paste the Zapier URL, give it a label (e.g. "Zapier — new leads"), and set its scope (your whole workspace or one bot). The URL must be https:// (Zapier's always is).

  3. 3

    Enable the events you want delivered

    Which events reach a destination is controlled in Settings → Notifications: tick the Webhook column for each event you want (the column unlocks once you have a destination on an eligible plan). Several events are off by default, so nothing is delivered until you enable them here.

  4. 4

    Route per event with a Zapier Filter

    A destination delivers every event you enabled for it, each tagged with its event.type. To act on just one kind, add a Filter by Zapier step after the trigger: only continue if Event Type (exactly matches) new_lead. Use one Zap per event type, or branch with Paths. (The Adoomi Zapier app described above has a separate trigger for each event, so it needs no filter step.)

  5. 5

    Map the fields and turn it on

    Trigger the event once so Zapier captures a sample — for new_lead, submit a test lead through your bot. Zapier shows the parsed payload; map fields like data.lead_email and data.lead_name into your downstream action (Slack message, Google Sheets row, CRM contact, …), then publish the Zap.

What the payload looks like

Each delivery is a JSON envelope with a fixed event object and an event-specific data object. Here is a new_lead example — see the webhook delivery reference for all eight event types, headers, and signature verification.

{
  "event": {
    "id": "b6f5a0c1-2d3e-4f50-8a1b-9c7d6e5f4a3b",
    "type": "new_lead",
    "version": "1.0",
    "occurred_at": "2026-05-14T09:15:30.000Z",
    "tenant_id": "7df8d8f2-0df7-48a8-9f52-5d42b4a67df0",
    "bot_id": "f9c3b0de-6f5b-4a22-bc8f-dac26351d6de"
  },
  "data": {
    "lead_id": "a1b2c3d4-e5f6-4789-a0b1-c2d3e4f5a6b7",
    "lead_name": "Sam Example",
    "lead_email": "sam@example.com",
    "lead_phone": "+15555550123",
    "lead_message": "Do you ship to Germany?",
    "page_url": "https://acme.example/pricing",
    "conversation_id": "d4c3b2a1-f6e5-4987-b1a0-7b6c5d4e3f2a",
    "chatbot_id": "f9c3b0de-6f5b-4a22-bc8f-dac26351d6de"
  }
}

Verifying signatures (optional)

Every request carries an HMAC-SHA256 signature in the X-AIChat-Signature-256 header. Zapier's Catch Hook does not check it, so you can ignore it for trusted internal Zaps. If you want to verify, add a Code by Zapier step using your destination's signing secret — the algorithm and a reference verifier are in the delivery reference.

Adoomi