Skip to main content
Each outbound webhook event has its own reference page with routing notes, payload shape, and recommended handling patterns. Use this hub to jump directly to the event you need to implement.

​
Contact and lead events

lead.captured

Fired when a new lead/contact is created.

contact.job_changed

Fired when lead/job metadata changes.

​
Interaction events

interaction.captured

Fired when a new interaction is recorded.

​
Booking events

booking.created

Fired when a booking is confirmed via a Klipy scheduling link.

booking.rescheduled

Fired when an existing booking is moved to a new time.

booking.cancelled

Fired when a confirmed booking is cancelled.

​
Deal events

deal.created

Fired when a new deal record is created.

deal.contact_added

Fired when a contact is attached to a deal.

deal.moved

Fired when a deal stage changes.

deal.closed

Fired when a deal is won or lost.

​
Meeting events

meeting.starting_soon

Fired when a scheduled meeting is about to begin.

meeting.completed

Fired when a meeting transitions to completed state.

meeting.no_showed

Fired when a meeting ends with no external participants present.
Klipy can add new event types over time. New pages may be added to this hub as the event catalog evolves.

​
Payload tips

  • Treat type as your primary routing key.
  • Use data.id or the nested object id as an idempotency key where available.
  • Handle unknown event types defensively so your endpoint remains forward-compatible.
Last modified on July 30, 2026