Connect Zapier

Zapier connects Hilal Chatbot to 5,000+ apps. Pick an event (a captured lead, a started conversation, an escalation), point it at a Zapier “Catch Webhook” trigger, and trigger Slack messages, Google Sheets rows, Salesforce updates, anything Zapier supports.

In this guide:

• The five event types
• Create a Zapier webhook
• Register it in Hilal Chatbot
• Test the delivery
• Read the delivery log
• Verify HMAC signatures

The five event types

Hilal Chatbot fires these events:

Event status: lead.captured is fully wired today. The other four originate in the chatbot backend and are wired in the companion backend PR — verify on the in-app changelog whether they’re live for your tenant.

Step 1: Create a Zapier webhook trigger

1. In Zapier, create a new Zap.
2. Choose Webhooks by Zapier as the trigger.
3. Pick Catch Hook.
4. Zapier gives you a webhook URL (e.g., https://hooks.zapier.com/hooks/catch/12345/abcdef/). Copy it.

Step 2: Register the webhook in Hilal Chatbot

In Hilal Chatbot, go to Integrations → Webhooks (or per-chatbot Chatbot → Actions → Webhooks).

Click New webhook.

• URL — paste the Zapier hook URL. Must be HTTPS.
• Events — tick the events you want (lead.captured, etc.).
• Description — “Zapier — leads to Salesforce” (your future self will thank you).

Click Save.

Screenshot: The Zapier trigger configuration in Hilal Chatbot’s webhooks page.

Step 3: Test the delivery

Click the Test button on the webhook row. Hilal Chatbot sends a synthetic test payload to the URL.

In Zapier, refresh — the test payload appears as a sample event. Use it to map fields in your Zap (e.g., lead.email → Salesforce Contact Email).

Step 4: Continue building your Zap

In Zapier:

1. Build the action (e.g., Salesforce → Create Lead).
2. Map fields from the Hilal Chatbot payload.
3. Test the full Zap.
4. Turn it on.

Now every lead.captured event in Hilal Chatbot fires the Zap.

Step 5: Read the delivery log

Click View deliveries on a webhook row. You’ll see every delivery attempt with:

• Timestamp
• HTTP status returned by Zapier
• Response body (truncated)
• Latency

Failed deliveries retry with exponential backoff (up to several attempts).

Screenshot: The webhook delivery log showing successes, failures, and retries.

HMAC signatures

Every delivery includes a signature in the X-Webhook-Signature header — HMAC-SHA256 of the body using a secret unique to your webhook.

To verify in Zapier (advanced — usually not needed for trusted integrations), use a Code by Zapier step that recomputes the HMAC and compares. For most use cases, Zapier’s HTTPS endpoint is enough.

For your own webhook listeners (not Zapier), always verify the signature before trusting payload contents.

Tips

• One webhook per Zap. It’s easier to debug one event at a time than a webhook firing five different events into one Zap.
• Use lead.captured first. It’s fully wired today and is the most common automation trigger.
• Don’t subscribe to message.received casually. It fires on every user message — that’s potentially thousands of Zapier task runs per day.

Troubleshooting

• Test fires but Zap doesn’t run. Zap may not be turned on, or the trigger setup may be incomplete in Zapier.
• Delivery log shows 4xx errors. Zapier rejected the payload (rare) — usually a hook URL typo.
• Delivery log shows 5xx errors. Zapier had a temporary issue. The retry backoff handles it; if persistent, check Zapier status.

What’s next