Events, pushed to you
When a conversation ends, a lead qualifies or a browser task finishes, your systems should not have to find out by polling. Point a webhook at your endpoint and the event arrives as it happens.
The escape hatch from our integrations
You are never limited to the CRMs we happen to support. Anything that accepts an HTTP request can receive the same data.
Documented payloads
Every event type ships with its shape and a sample, so you build against something concrete rather than reverse-engineering a first delivery.
One endpoint per job
Subscribe each endpoint to only the events it needs, instead of filtering a firehose on your side.
Pull as well as push
The REST API covers what webhooks do not, so you can reconcile state as well as react to events.
What teams build with it
Three jobs this does the day you turn it on.
Into the system we do not integrate with
We ship Pipedrive and HubSpot. For everything else - your own back office, an internal database, a niche CRM - a webhook puts the same data where you need it.
Trigger the rest of the workflow
A new lead can open a ticket, start an onboarding sequence or alert a channel, without anyone watching a dashboard for it.
Keep your own record
Mirror conversations into your warehouse as they happen, so your reporting does not depend on exporting ours.
Where you set this up
The same build screen every feature is configured from — this row is the one you would touch.
Under the hood
The details you will want before you commit.
How it works
Add an endpoint
Point it at your URL in Integrations and choose the events it should receive.
Check the sample
Read the documented payload for each event and build your handler against it.
Go live
Events start arriving as conversations, leads and tasks happen.
Where it earns its keep
Industry playbooks that lean on this piece — what to build first, and what to charge.
Frequently asked questions
Use a webhook when you want to know the moment something happens, and the API when you want to ask for the current state. Most integrations end up using both.
Every event type has a documented shape and a worked sample in the dashboard, so you can build against it before wiring anything up.
Yes. Each endpoint subscribes to the events it cares about, so your billing system is not woken up by every chat message.
For a webhook, usually yes - or an automation tool that accepts one. If you just want leads in Pipedrive or HubSpot, use the CRM integration instead and skip the plumbing.
How it compares
Side by side with the tools people usually weigh this against.
SuperCognit vs Botpress →
Botpress is a developer-oriented platform for building conversational AI with a visual flow editor.
SuperCognit vs Voiceflow →
Voiceflow is a conversation-design platform used by teams to prototype and ship chat and voice assistants.
SuperCognit vs Chatfuel →
Chatfuel is a chatbot platform for Messenger, Instagram and WhatsApp, focused on marketing automation flows.