Overview
This node acts as a webhook trigger for SimplyBook.me events. It listens for specific events from the SimplyBook.me booking system and triggers workflows in n8n when those events occur. This is useful for automating processes based on booking activities, such as sending notifications, updating CRM systems, or managing invoices.
Common scenarios include:
- Triggering a workflow when a new booking is created to send confirmation emails.
- Reacting to booking cancellations to update availability or notify staff.
- Processing new invoices automatically for accounting purposes.
- Handling updates to booking details to keep external systems synchronized.
- Responding to new client registrations or new offers being created.
Properties
| Name | Meaning |
|---|---|
| Event | The type of SimplyBook.me event to listen for. Options: |
| - Cancelled Booking: Triggers when a booking is canceled | |
| - New Booking: Triggers when a new booking is created | |
| - New Invoice: Triggers when a new invoice is created | |
| - Updated Booking Details: Triggers when booking details like date, time, service, provider are updated | |
| - New Client: Triggers when a new client is created | |
| - New Offer: Triggers when a new offer is created |
Output
The node outputs the raw JSON payload received from SimplyBook.me via the webhook. This data contains detailed information about the triggered event, such as booking details, client info, invoice data, or offer specifics depending on the event type.
If binary data were involved (not indicated here), it would be summarized accordingly, but this node only outputs JSON data.
Dependencies
- Requires an API key credential for SimplyBook.me with appropriate permissions.
- The node must be configured with the base URL of the SimplyBook.me instance.
- The node registers and manages webhooks on SimplyBook.me via its API, so network connectivity and valid credentials are essential.
Troubleshooting
- Webhook registration issues: If the webhook does not trigger, ensure the node has correct credentials and that the webhook URL is accessible from SimplyBook.me.
- Event mismatch: Make sure the selected event matches the expected incoming webhook event; otherwise, the workflow will not trigger.
- Permission errors: Verify that the API key used has permission to manage webhooks and access event data.
- Duplicate webhooks: The node checks for existing webhooks before creating new ones, but manual changes in SimplyBook.me might cause conflicts.
- Error messages during webhook creation/deletion: Usually indicate credential or network problems; recheck API keys and endpoint URLs.