What Are Webhooks?#
Imagine you run a business and need to deliver important messages from one system to another—just like a courier delivering a package. Webhooks work in a similar way, acting as a digital courier 🚚 that delivers real-time updates between platforms.A webhook 🪝 is an automated message sent from WellnessLiving to another system whenever a specific event occurs. For example, if a client books an appointment, your system can receive instant notification about that booking. This eliminates the need to manually check for updates, allowing your software to stay in sync with WellnessLiving in real time.Each webhook contains a payload 💰, which is like the package that the courier delivers. The payload includes details about the event, such as the name of the client who booked an appointment, the time of the session, and any payment details.How Can Webhooks Be Used?
Webhooks allow businesses to send real-time data from WellnessLiving to third-party platforms and custom applications, enabling seamless data exchange and automation.
1. Connect WellnessLiving with Other Business ToolsMany platforms support webhooks, allowing them to receive real-time updates from WellnessLiving. Here are some examples:CRM platforms (e.g., HubSpot, Salesforce, GoHighLevel) → Automatically update client records when new sign-ups, purchases, or membership changes occur.
Marketing tools (e.g., Mailchimp, ActiveCampaign) → Add new clients to email lists or trigger automated marketing sequences based on their activity.
2. Automate Workflows with No-Code PlatformsIf you're using tools like Zapier or Make you can create automated workflows that trigger actions based on webhook events from WellnessLiving:When a new client is added, automatically create a new contact in Google Contacts.
When a purchase is made, send a Slack message to your sales team.
When an appointment is booked, add it to a Google Calendar.
3. Enable Advanced Custom ApplicationsFor developers, webhooks provide the flexibility to build powerful integrations tailored to your business needs:
Custom dashboards → Aggregate webhook data in a private dashboard to track key business metrics.
AI-powered customer interactions → Send client activity data to AI chatbots or recommendation engines.
Bespoke client experiences → Use webhook data to trigger unique customer engagement strategies, such as loyalty programs or custom messaging.
Available Webhooks in WellnessLiving
WellnessLiving provides webhooks for key business activities, enabling seamless data exchange. Below are the webhooks currently available:
1
Business
Triggered when Business details are updated, e.g. Business name, policies, settings
2
Location
Triggered when A new location is created or updated, e.g. Address, contact details, hours
3
Staff Profile
Triggered when A staff member is added or updated, e.g. Name, role, availability
4
Schedule
Triggered when Class schedules are created or updated, e.g. Service name, date/time, instructor
5
Service
Triggered when An appointment is booked or changed, e.g. Client name, service, time slot
6
Client Profile
Triggered when A client profile is created or updated, e.g. Contact info, membership status
7
Purchases
Triggered when A purchase or refund occurs, e.g. Item details, price, payment method
Step 1: Request Webhook Activation
Step 2: Share your Webhook listener information
To enable webhooks for your WellnessLiving account:
2. Include the following details in your request:Webhook events you want to enable
The URL(s) where webhook events should be sent
A few tips while using WellnessLiving Webhooks
Each webhook event includes metadata about the webhook itself. The request header provides contextual details for the receiver, while the body contains the payload, which encapsulates data relevant to the webhook's event topic.
All webhooks are delivered via HTTP POST requests. To prevent processing delays, ensure that any rate-limiting policies are adjusted or disabled for incoming webhook events.
• Content-Type: application/json
• x-topic: The webhook topic.
• x-signature-256: SHA256 hash of the payload using webhook key.
• x-generated-at: Indicates when the webhook payload was generated.
• x-sent-at: Indicates when the webhook was sent.
• x-payload-key: A hash of the payload, which can be used for managing and handling duplicate webhooks.
Our webhook engine requires a 200 OK or 201 Created response to confirm a successful integration. Any other status code (4XX or 5XX) will trigger a retry mechanism for the webhook delivery.
Our webhook engine retries failed deliveries for up to three days, using an exponential backoff strategy to prevent excessive requests and maintain system integrity. As the receiver, we recommend utilizing the x-generated-at header to verify the webhook's timestamp, ensuring outdated events are ignored and avoiding duplicate processing of already updated records.
All webhooks can be verified using the x-signature-256 header, which contains a SHA-256 hash of the webhook body. This hash is generated using the subscriber's webhook key, issued at the time of subscription creation.
Final Thoughts#
Webhooks are a game-changer for businesses looking to integrate WellnessLiving with other platforms. Whether you're connecting to a CRM, automating workflows with Zapier, or building a custom solution, webhooks provide real-time, automated data sharing that keeps everything up to date.