> ## Documentation Index
> Fetch the complete documentation index at: https://klipy.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Which webhook events are available?

> Outbound webhook events and per-event documentation.

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

<CardGroup cols={1}>
  <Card title="lead.captured" icon="webhook" href="/docs/webhooks/lead-captured">
    Fired when a new lead/contact is created.
  </Card>

  <Card title="contact.job_changed" icon="webhook" href="/docs/webhooks/contact-job-changed">
    Fired when lead/job metadata changes.
  </Card>
</CardGroup>

## Interaction events

<CardGroup cols={1}>
  <Card title="interaction.captured" icon="webhook" href="/docs/webhooks/interaction-captured">
    Fired when a new interaction is recorded.
  </Card>
</CardGroup>

## Booking events

<CardGroup cols={1}>
  <Card title="booking.created" icon="webhook" href="/docs/webhooks/booking-created">
    Fired when a booking is confirmed via a Klipy scheduling link.
  </Card>

  <Card title="booking.rescheduled" icon="webhook" href="/docs/webhooks/booking-rescheduled">
    Fired when an existing booking is moved to a new time.
  </Card>

  <Card title="booking.cancelled" icon="webhook" href="/docs/webhooks/booking-cancelled">
    Fired when a confirmed booking is cancelled.
  </Card>
</CardGroup>

## Deal events

<CardGroup cols={1}>
  <Card title="deal.created" icon="webhook" href="/docs/webhooks/deal-created">
    Fired when a new deal record is created.
  </Card>

  <Card title="deal.contact_added" icon="webhook" href="/docs/webhooks/deal-contact-added">
    Fired when a contact is attached to a deal.
  </Card>

  <Card title="deal.moved" icon="webhook" href="/docs/webhooks/deal-moved">
    Fired when a deal stage changes.
  </Card>

  <Card title="deal.closed" icon="webhook" href="/docs/webhooks/deal-closed">
    Fired when a deal is won or lost.
  </Card>
</CardGroup>

## Meeting events

<CardGroup cols={1}>
  <Card title="meeting.starting_soon" icon="webhook" href="/docs/webhooks/meeting-starting-soon">
    Fired when a scheduled meeting is about to begin.
  </Card>

  <Card title="meeting.completed" icon="webhook" href="/docs/webhooks/meeting-completed">
    Fired when a meeting transitions to completed state.
  </Card>

  <Card title="meeting.no_showed" icon="webhook" href="/docs/webhooks/meeting-no-showed">
    Fired when a meeting ends with no external participants present.
  </Card>
</CardGroup>

<Info>
  Klipy can add new event types over time. New pages may be added to this hub as the event catalog evolves.
</Info>

## 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.