Push every chatbot lead, message, or escalation to Google Sheets, Airtable, Salesforce, Mailchimp, PagerDuty, or any other app Zapier supports. Signed webhooks, 2-second delivery, zero configuration.
Works with Zapier free plan · HMAC-signed · Automatic retries
No marketplace app to install — just standard webhook plumbing.
Choose "Catch Hook" as the trigger. Zapier gives you a unique webhook URL — copy it.
Go to Webhooks & Integrations → Add Webhook. Paste the Zapier URL, pick which event types to subscribe to (lead.captured, message.received, etc.), and save.
Submit a lead on your chatbot (or click "Send test" in the InsiteChat dashboard). Zapier captures the payload so you can map fields in the next step.
Add any downstream Zapier actions: create a row in Google Sheets, add a Mailchimp subscriber, push to Salesforce, post to Discord — whatever your stack needs. Turn on the Zap.
The escape hatch to any tool we don't integrate with directly.
InsiteChat fires a signed HTTPS POST for every event. Zapier's "Webhooks by Zapier" trigger receives it as a regular webhook — no special Zapier plugin needed, no OAuth dance.
Subscribe to lead.captured, message.received, conversation.started, or conversation.escalated. Route each event type to a different Zap so leads go to your CRM and escalations go to PagerDuty.
Anything Zapier can reach — Google Sheets, Airtable, HubSpot, Salesforce, Mailchimp, Klaviyo, Notion, Monday, Asana, ClickUp, Trello, Slack, Discord, PagerDuty. Chain multi-step Zaps as needed.
Events hit Zapier within two seconds of the triggering action. No polling, no batch delays — faster than most native integrations.
If Zapier's endpoint is temporarily unavailable, InsiteChat retries 3 times with exponential backoff (1 min, 5 min, 15 min) so transient network issues don't lose events.
Every webhook delivery (success or failure) is logged in your InsiteChat dashboard with status code and response body. When a Zap breaks at 2am, you'll have the logs to debug it.
Three patterns you can copy on day one.
We natively integrate with HubSpot, but Zapier lets you push leads into Pipedrive, Salesforce, Zoho, Freshsales, Close, Copper, or any other CRM in the Zapier catalog.
Use Zapier Paths to branch by lead fields — send "enterprise" leads to your sales Slack, "student" leads to a newsletter, and "spam" leads to /dev/null. Zapier handles the logic.
Don't want to write webhook handlers? Use Zapier to fan out every chatbot event into Gmail, SMS via Twilio, PagerDuty, Telegram, or internal Slack channels with zero code.
Each event ships a well-documented JSON payload — see full schemas in our docs.
Every webhook payload is signed with HMAC-SHA256 using a per-webhook secret. The signature lives in the X-InsiteChat-Signature header. Failed deliveries retry 3 times with exponential backoff. Every attempt — success or failure — is recorded in your InsiteChat delivery log with status code and response body so you can debug any Zap that breaks.
Everything you need to know about routing InsiteChat to Zapier.
No. We use the standard "Webhooks by Zapier" trigger, which comes built-in on every Zapier plan. No special app to install, no OAuth to approve, no waiting for marketplace review.
Any Zapier plan, including the Free tier. Webhook triggers are supported on every plan. Higher Zapier tiers just give you more tasks a month and multi-step Zaps.
We sign each payload with HMAC-SHA256 using a shared secret. Zapier doesn't verify the signature by default (which is fine for most use cases), but if you want signature verification, route through a Code by Zapier step that checks the X-InsiteChat-Signature header.
Four event types: lead.captured (visitor submits the lead form), message.received (any visitor message), conversation.started (first message of a new session), and conversation.escalated (visitor asks to talk to a human).
Yes. Create multiple webhooks in InsiteChat, each with a different Zapier catch-hook URL, each subscribed to different event types. So lead.captured goes to your CRM Zap and conversation.escalated goes to your on-call Zap.
InsiteChat retries failed deliveries 3 times with exponential backoff (1 min, 5 min, 15 min). If all retries fail, the event stays logged in your InsiteChat delivery history so you can replay it manually.
Yes. Anything that accepts an HTTPS POST works — Make, n8n, Pipedream, Automate.io, tray.io, self-hosted flow engines. We don't lock you into Zapier.
Free on every InsiteChat plan, including the free tier. You pay whatever Zapier charges for tasks — which is often free on Zapier's starter tier for low-volume sites.
Free on every plan. Works with Zapier's free tier. First Zap running in under 10 minutes.
Get started free