Webhook event reference Review the current OmniLab webhook event families and the event names used in subscriptions.
This reference lists the current event families that can be routed through OmniLab webhooks. In subscription rules, use the plain event type such as reward.won.v1 or booking.created.v1.
Use the event type, not the transport subject
OmniLab subscription rules use the plain event type name. You do not need to include any internal transport prefix when you prepare your event list.
Filter Use it when tenant_id=<tenant-id>The callback should receive the full tenant feed group_id=<group-id>The callback should receive only one organisation or group interaction_id=<interaction-id>The callback should receive events for one campaign or experience
Event type When it fires Common downstream use touchpoint.page_visit.v1A touchpoint page is viewed Traffic and funnel analytics touchpoint.participated.v1A participant enters the experience Participation counters and CRM activity touchpoint.participation_form_filled.v1A participation form is submitted Lead capture workflows touchpoint.started.v1A touchpoint session starts Journey analytics and game-state tracking touchpoint.completed.v1A touchpoint session completes Completion funnels and achievement logic touchpoint.terms_accepted.v1Terms or consent are accepted Consent audit trails cta.clicked.v1A configured CTA is clicked Link attribution and conversion tracking question.answered.v1A question or quiz answer is submitted Quiz analytics and scoring flows feedback.submitted.v1Feedback or satisfaction input is submitted Voice-of-customer pipelines
Event type When it fires Common downstream use reward.eligible.v1A participant becomes eligible for a reward Draw and leaderboard automation reward.won.v1A participant wins a reward Fulfilment, CRM, and loyalty updates reward.lost.v1A participant loses a reward outcome Consolation journeys and analytics reward.redeemed.v1A won reward is redeemed Redemption reporting and POS reconciliation reward.temporary_won.v1A temporary win state is recorded Multi-stage reward workflows reward.temporary_lost.v1A temporary loss state is recorded Multi-stage reward workflows reward.temporary_blocked.v1A temporary reward state is blocked Exception handling and audit flows
Event type When it fires Common downstream use contact.created.v1A new contact is created Contact sync and enrichment contact.identified.v1An anonymous visitor is linked to an identified contact Identity stitching contact.authenticated.v1A contact authenticates Login tracking and secure workflow triggers notification.sent.v1OmniLab sends a notification Delivery reporting and observability
Event type When it fires Common downstream use participation.checked_in.v1A participant is checked in to an activity Attendance reporting and staffing flows booking.created.v1A booking is created Booking portals and confirmation sync ticket.confirmed.v1A ticket is confirmed Capacity and reminder workflows ticket.canceled.v1A confirmed ticket is canceled Cancellation notices and seat recovery ticket.waitlisted.v1A participant moves onto the waitlist Waitlist messaging booking.deleted.v1A booking is deleted Cleanup and reconciliation ticket.deleted.v1A ticket is deleted Cleanup and reconciliation participation.deleted.v1A participation record is deleted Cleanup and reconciliation
Typical booking.created.v1 payload fields { "booking_id" : "booking_123" , "event_id" : "event_456" , "event_name" : "VIP styling session" , "tickets_number" : 2 , "reserver_id" : "contact_789" , "host_id" : "host_001" , "ticket_type_id" : "ticket_type_vip" , "ticket_type_display_name" : "VIP" , "slot_start_date" : "2026-05-03T14:00:00Z" , "slot_end_date" : "2026-05-03T14:30:00Z" , "booked_at" : "2026-04-26T09:15:00Z" } Event type When it fires Common downstream use submission.created.v1A submission is created Intake pipelines submission.status_changed.v1A submission changes validation or review status Review workflow automation submission.amended.v1A submission is amended Audit trails and review updates submission.replaced.v1One submission replaces another Reconciliation and case handling
Event type When it fires Common downstream use smartlink.redirected.v1A Smart Link redirect happens Channel attribution and redirect analytics
