ZenotiHelp

Package webhook events

ZTZenoti Docs Team Updated September 2, 2026 3 min readGuide

Configure webhook events and notification settings for package lifecycle events in Zenoti.

Before you begin

  • You need the following permissions:

Permission: Edit (under Packages) β€” Required to configure package webhook and notification settings.

  • Your organization must have the Event Management System (EMS) enabled for webhook events to trigger.
  • Ensure your webhook endpoints are configured and accessible before enabling package events.

Steps

Configure package webhook events

Package webhooks trigger automatically when specific package events occur in the system.

  1. Navigate to Configuration > Integrations > Webhooks.
  2. In the Package Events section, enable the events you want to track:
  • Package Created β€” Triggers when a new package is created
  • Package Updated β€” Triggers when package details are modified
  • Package Purchased β€” Triggers when a guest purchases a package
  • Package Redeemed β€” Triggers when benefits are used from a package
  • Package Expired β€” Triggers when a package reaches its expiry date
  • Package Transferred β€” Triggers when a package is transferred between guests
  • Package Refunded β€” Triggers when a package purchase is refunded
  1. For each enabled event, configure the following:
  • Webhook URL β€” Enter the endpoint URL that will receive the webhook payload
  • Expand Fields β€” Select which package data to include in the webhook payload:
  • Basic Info β€” Package name, type, and status
  • Benefits β€” Included services, products, and quantities
  • Pricing β€” Package price, taxes, and payment details
  • Guest Info β€” Associated guest information
  • Center Info β€” Center where the package was purchased or redeemed
  1. Click Test Webhook to verify your endpoint receives the payload correctly.
  2. Click Save to activate the webhook events.

Note: Webhook events only trigger when the Event Management System (EMS) is enabled for your organization. Contact support if you need EMS activation.

Configure package expiry reminder notifications

Set up automated notifications to remind guests about upcoming package expirations.

  1. Navigate to Configuration > Notifications.
  2. In the Package Notifications section, click Package Expiry Reminders.
  3. Configure the reminder schedule:
  • Days Before Expiry β€” Enter how many days before expiration to send the reminder (e.g., 7, 14, 30)
  • Reminder Frequency β€” Choose how often to send reminders:
  • Single Reminder β€” Send one notification at the specified time
  • Multiple Reminders β€” Send reminders at multiple intervals
  1. Select the notification channels:
  • Email β€” Send email notifications to the guest's registered email address
  • SMS β€” Send text message notifications to the guest's mobile number
  • WhatsApp β€” Send WhatsApp messages to the guest's WhatsApp number
  1. For each enabled channel, customize the message content:
  • Subject Line (Email only) β€” Enter the email subject
  • Message Body β€” Enter the notification text using available merge fields:
  • {GuestName} β€” Guest's full name
  • {PackageName} β€” Name of the expiring package
  • {ExpiryDate} β€” Package expiration date
  • {RemainingBenefits} β€” List of unused benefits
  • {CenterName} β€” Center where the package was purchased
  1. Click Preview to see how the notification will appear to guests.
  2. Click Save to activate the expiry reminders.

Manage bulk webhook triggers

Process untriggered package update events in bulk when needed.

  1. Navigate to Configuration > System Tools > Webhook Management.
  2. In the Package Events section, click View Untriggered Events.
  3. Review the list of package update events that haven't been sent to webhooks.
  4. Select the events you want to process:
  • Use Select All to choose all untriggered events
  • Use individual checkboxes to select specific events
  1. Click Trigger Selected Events to send the webhook payloads.
  2. Monitor the Status column to confirm successful delivery.

Important: Bulk triggering processes events in the order they occurred. Large batches may take several minutes to complete.

Was this article helpful?
Your feedback helps us improve our documentation.