In short
- Nine events to choose from.Conversations, messages, handoffs, status, leads, contacts, ratings, bookings and usage.
- Signed with an open standard.Every delivery follows Standard Webhooks, so your server can prove it came from OneType.
- Retries for about three days.A failed delivery is retried on a schedule from 5 seconds up to 24 hours.
- A log you can replay.See every attempt for 30 days and send any event again with one click.
A lead that sits only in a chat tool is a lead that gets forgotten. A webhook is a message OneType sends to an address on your server whenever something happens. Use it to add leads to your CRM, open tickets, ping your team or update a dashboard, without anyone copying data by hand.
The events
- conversation.created: a visitor starts a conversation.
- conversation.message.created: a message is completed, by the visitor, the agent or your team.
- conversation.handoff.requested: the visitor or the agent asks for a person.
- conversation.status.changed: open, escalated, resolved, unresolved or failed.
- lead.captured and contact.identified: a visitor leaves contact details or is recognized as one of your signed-in users.
- usage.threshold.reached: your workspace reaches 80% or 100% of its monthly usage.
Each delivery carries the same object the REST API returns for that resource, so a message includes whether it was written by AI. You can subscribe an endpoint to some events or to all of them.
Set it up in the dashboard
In Developer, Webhooks, an owner or admin adds an https address and picks the events. The signing secret is shown once, so store it right away. Click Send test to deliver a signed ping and see the response code and timing. You can rotate the secret any time: for 24 hours both the old and new secret sign each delivery, so nothing breaks while you switch.
Deliveries you can rely on
Answer any 2xx within 10 seconds and the delivery counts. If your server fails or is slow, OneType retries after 5 seconds, 30 seconds, 2 minutes, 10 minutes, 30 minutes, 1 hour, 3 hours, 6 hours, 12 hours, then every 24 hours three times. Delivery is at least once, so store the webhook-id header, which stays the same on every retry, and ignore repeats. Order is not guaranteed.
An endpoint that only fails for three days is turned off, and owners see a banner with Turn back on. The delivery log keeps every attempt for 30 days with status, code, timing and a response excerpt, and Redeliver sends an event again.
Security
Every request is signed per Standard Webhooks with a timestamp, so you can reject old or replayed requests. OneType only delivers to public https addresses, never to private networks, and does not follow redirects. The developer docs include verification code for Node.js, Python and PHP.
Ideas for your first endpoint
- Add every lead.captured contact to your CRM or mailing list.
- Open a ticket in your helpdesk on conversation.handoff.requested.
- Alert your team channel when a conversation is escalated.
- Warn finance when usage.threshold.reached arrives.
Only owners and admins can see and manage endpoints, and secrets are never shown again after the first time. Other teammates do not see webhooks at all.