Skip to main content

Event Destinations

Event Destinations tell Kazenly what to do when an external system posts an inbound event (for example a booking). They live under Settings → Data & CRM → Event Destinations.

Only admins and managers can manage destinations. Pair this with API Keys that include the events.inbound scope.

Open Event Destinations​

  1. Open Settings.
  2. Under Data & CRM, select Event Destinations.

Page title: Event Destinations
Lead: map inbound OMS types to contact fields and an optional approved Utility. Your OMS does not send template names — this page owns the send map.

Empty: No destinations yet · Without a destination, inbound events are rejected until you add one.

Add a destination​

  1. Click Add destination, or Stampede preset / Apply Stampede preset to start from a booking map.
  2. In New destination / Edit destination, set:
    • Event type (for example booking.created)
    • Display name
    • Guest name path (optional) — updates the contact display name
    • Active
  3. Under Field map, add rows (Data path → Contact field). Use Add mapping for more rows. Define fields first under Contact Fields.
  4. Optionally set Utility template name and Language, plus Template body parameters (Add body parameter). Leave the template blank for upsert-only (no WhatsApp send). Pilot send is approved Utility only — not Marketing.
  5. Click Save destination (or Cancel).

Advanced JSON lets you paste a JSON draft of the map, then Apply JSON to editor.

List actions​

Each destination row shows field-map count and either a Utility name or upsert only (no send). Use Edit or Remove.

Remove destination? warns that events of that type will be rejected until you add a new destination; inbound history is kept. Confirm Remove or Keep.

Inbound events (last 20)​

Below the list, Inbound events (last 20) shows recent outcomes only — payloads are never stored or shown.

  • Filters: All types / All outcomes (accepted · duplicate · rejected · send_failed)
  • Refresh reloads the log
  • Empty: No inbound events yet.
  • When a contact was resolved, Contact #N opens that person on Contacts (and closes the profile clears the deep link)