Zapier integration · Automation
Send chat events to any Zap.
SuperBot connects to Zapier through a “Webhooks by Zapier → Catch Hook” trigger. You paste the hook URL, pick events, and SuperBot POSTs each event to it as JSON. From there your Zap can send it to any app Zapier supports. No SuperBot app inside Zapier is needed.
- Catch Hook URL
- SuperBot → your Zap (JSON events)
- Free, Starter & Pro
How the Zapier integration works
Zapier is the route to tools SuperBot does not connect to directly: Google Sheets, Airtable, Notion, a help desk, an SMS tool. The Catch Hook receives the event name, the event data, and a timestamp, and Zapier lets you map those fields into the next step.
The transport is the same as SuperBot's custom webhooks, including the optional signing secret. Deliveries that fail with a network error or a 5xx response are retried with backoff.
- New lead captured
- Form submitted
- New conversation started
- Conversation escalated to a human
Highlighted: the events most teams keep for this connector. You choose per connection.
What gets sent
| From SuperBot | In Zapier |
|---|---|
| event | lead.captured, form.submitted, conversation.created, or conversation.escalated |
| data.name / data.email / data.phone | Visitor details, when known |
| data.message / data.source | Latest message and where it came from |
| occurredAt | ISO timestamp of the event |
Extra fields such as conversationId, siteId, or form_name are included when the event has them. Use “Send test” first so Zapier has a sample to map from.
Connect Zapier to SuperBot
- In Zapier, create a Zap with the trigger “Webhooks by Zapier” and the event “Catch Hook”. Copy the hook URL.
- In SuperBot, open Dashboard → Integrations, find Zapier, select Connect, and paste the URL into “Zapier catch hook URL”.
- Optionally add a signing secret if a later step will check the X-SuperBot-Signature header.
- Under “Send these events”, keep only the events you want this connection to receive. All four are ticked by default: new lead captured, form submitted, new conversation started, and conversation escalated to a human.
- Select “Connect & verify”, then “Send test” so the sample event (Test Lead) reaches Zapier.
- Back in Zapier, test the trigger, map the fields into your action, and turn the Zap on.
Don't have a workspace yet? Sign up free — no card needed — then open Dashboard → Integrations.
Permissions and privacy
- Only the URL you paste receives data. It must be a public HTTPS address; private and internal network addresses are refused, and redirects are not followed.
- Payloads include visitor name, email, phone, company, and message when known — whatever your Zap does next is governed by your Zapier account.
- The optional signing secret is encrypted before storage.
- Turn off the Zap, or Disconnect in SuperBot, to stop deliveries.
What teams use Zapier with SuperBot for
- Log every lead in a spreadsheet
Catch “New lead captured” and append a row to Google Sheets or Airtable.
- Text the on-call person on escalation
Catch “Conversation escalated to a human” and send an SMS or push notification through your Zap.
- Reach a CRM SuperBot doesn't list
Map the event into any CRM with a Zapier action when it is not HubSpot, Salesforce, or Pipedrive.
- Multi-step routing
Use Zapier filters and paths to send enterprise leads one way and everyone else another.
FAQ
Zapier integration questions, answered.
Ready to try it? Start free or compare plans. Every integration is on every plan.
Is there a SuperBot app in the Zapier directory?
No. You don't need one. SuperBot sends events to a Webhooks by Zapier Catch Hook, which works on any Zap.
Which SuperBot events can trigger a Zap?
New lead captured, form submitted, new conversation started, and conversation escalated to a human. You choose which ones when you connect.
Can Zapier send data back into SuperBot?
Not through this connector. It is one-way: SuperBot sends events out to your Zap.
What if my Zap is off when an event fires?
SuperBot retries network errors and 5xx responses a few times, then records the error on the connection card. Events are not stored for replay after that.