Automations and webhooks
Send Pingu chat events to Zapier, Make, n8n or your own systems the moment they happen.
Updated Sep 11, 2026
Automations send events from your chats to the other tools your business uses. When a conversation starts, a visitor sends a message, the AI replies or a chat ends, Pingu sends the details to a URL you choose.
Point it at Zapier, Make or n8n to connect Pingu to thousands of apps without code, or at your own API to build exactly the flow you need.
Set up a webhook
- Get a webhook URL. Create a webhook trigger in the tool that should receive the events, such as Catch Hook in Zapier, a custom webhook in Make, or a Webhook node in n8n, and copy its URL. You can also use an
https://address in your own system. - In the dashboard, open Automations and select Add webhook.
- Paste the URL, add a description, and choose the events to send.
- Select Save.
- Select Send test event. The delivery history shows whether your system received it, with the response code and time.
Events you can send
| Event | When it's sent |
|---|---|
conversation.started | A visitor starts a new chat |
message.received | A visitor sends a message |
message.ai_replied | The AI answers the visitor |
conversation.ended | A chat is closed |
Check the signature
Each webhook has its own signing secret. Pingu signs every request in a header, so your system can check that the event really came from Pingu:
X-Pingu-Signature: t=1760000000,v1=<HMAC-SHA256 of "<t>.<body>">
Checking the signature is optional, but recommended for your own APIs.
Reliable delivery
If your system doesn't answer, Pingu tries again after 1 minute, 5 minutes, 30 minutes, 2 hours and 6 hours. A webhook that keeps failing for 3 days is turned off automatically, and you can turn it back on with one click.
Common issues
The test event fails. Check that the URL is correct, starts with https://, and that the receiving tool is turned on and listening for requests.
My webhook was turned off. It failed for 3 days in a row. Fix the receiving system, then turn the webhook back on in Automations.
Still need help?
Our team is happy to take a look.
