IntelliIntelli Docs
Reference

Webhooks

Send Intelli data to external systems, and let external systems trigger chatbot flows or template messages.

Webhooks connect Intelli to the rest of your stack. Manage them at Dashboard → Settings → Webhooks, which has two tabs: Outbound Webhooks (Intelli calls your systems) and Inbound Webhooks (your systems call Intelli).

Plan availability

Webhooks are included on the Enterprise plan. On other plans they are a $5/mo add-on; add the Webhook integration from Billing to unlock inbound and outbound webhooks. Without either, the Webhooks page shows an upgrade notice instead of the tabs.

Outbound webhooks: send data out

Outbound webhooks push data to external systems like your CRM, Make, or Zapier. Each endpoint you send to is a destination.

Webhooks settings with Outbound Webhooks selected, the Inbound Webhooks tab, Add Destination, and a destination table showing POST methods, enabled status toggles, and delivery counts. Destination names, URLs, and sidebar identity details are blurred.

Adding a destination

  1. On the Outbound Webhooks tab, click Add Destination.
  2. In the Add Webhook Destination dialog, fill in:
    • Name: e.g. "Zapier Lead Capture".
    • Webhook URL: the endpoint to call.
    • HTTP Method: POST, GET, PUT, or PATCH.
    • Signing Secret (optional): used for HMAC-SHA256 signature verification so the receiver can confirm the call came from Intelli.
  3. Click Create Destination.
Add Webhook Destination dialog with Name and Webhook URL placeholders, POST selected, an empty optional Signing Secret field, Cancel, and Create Destination. Background details are blurred.

Destinations appear in a table showing the URL, method, an on/off status toggle, and delivery stats (success and failure counts). Open a row's three-dot menu to choose Test Webhook to fire a test delivery, or Delete to remove the destination. Send test deliveries only to an endpoint you control.

Outbound destination three-dot menu open with Test Webhook and Delete actions. Status toggles and delivery counts remain visible; destination names, URLs, and sidebar identity details are blurred.

Inbound webhooks: trigger Intelli from outside

Inbound webhooks give you a URL that an external system (Cal.com, Zapier, Make, your own backend) can call to start a chatbot flow or send a template message to a contact.

Creating an inbound webhook

  1. On the Inbound Webhooks tab, click Create Webhook.
  2. In the Create Inbound Webhook dialog, fill in:
    • Name: e.g. "Cal.com Booking" or "New Lead from Website".
    • WhatsApp Number: which of your numbers the action uses. Pick the number your contacts message; templates belong to it, and replies from any other number are rejected.
    • Action Type: Start Chatbot Flow or Send Template Message.
    • Depending on the action, pick the Chatbot Flow to start, or the Template to send (approved templates only).
    • Require API Key (optional): when on, callers must send an X-API-Key header. The key is generated after creation.
  3. Click Create Webhook.
Create Inbound Webhook dialog with an example Name placeholder, Action Type menu showing Start Chatbot Flow and Send Template Message, Require API Key toggle, and Create Webhook. The WhatsApp number and background details are blurred.

The Webhook Created Successfully dialog shows the webhook URL to paste into your third-party service. If you required authentication, the API key. Save the key immediately: it is not shown again (though you can Copy API Key or Regenerate API Key later from the webhook's menu).

Mapping the payload: Configure Webhook

Intelli needs to know which contact an incoming payload is about. Open a webhook's menu and choose Configure Webhook:

  • Detected payload fields: after the first request arrives, the dialog lists the fields it found; click one to add it to a mapping. If nothing has arrived yet, send a test request from your external service first.
  • Contact Match Field: pick (or type) the payload path that identifies the contact, e.g. attendees.0.email or phone_number. An optional formatter can clean the value up.
  • Create contact if not found: toggle on to auto-create a new contact from the payload data when no match exists.
  • Mappings: for Send Template Message, map template variable numbers to payload field paths; for Start Chatbot Flow, map payload fields to contact fields.

Click Save Configuration when the contact matching and mappings are ready.

Configure Webhook dialog with detected payload field paths, a phone-number Contact Match Field, Strip + formatter, enabled Create contact if not found toggle, and mappings to Full Name and Email. Add Row and Save Configuration are visible; background details are blurred.

Testing and logs

Each inbound webhook's menu also offers Test Webhook and View Logs. Test only with a contact and WhatsApp number you control, since the webhook can start a flow or send a template message.

Inbound Webhooks tab with Create Webhook and a row menu offering Copy URL, Configure Webhook, Test Webhook, View Logs, and Delete. Webhook names, full URLs, flow and template names, and sidebar identity details are blurred.

The logs dialog (Webhook Analytics) shows trigger history, delivery stats, and processing results, so you can see exactly what each call did. Click Refresh to load the latest results.

Webhook Analytics dialog with Total Triggers, Successful, Errors, and Opened counters; a history table with Sent and Not Found statuses, timestamps, and responses; and Refresh and Close controls. The webhook name, contact phone numbers, and background details are blurred.

What's next

  • Build the flow your webhook triggers → Chatbots
  • Create the templates it sends → Templates

On this page