Webhooks let you receive HTTP POST requests when events happen in meetergo. Use them to sync bookings with your CRM, trigger workflows, or update your application in real-time.Documentation Index
Fetch the complete documentation index at: https://developer.meetergo.com/llms.txt
Use this file to discover all available pages before exploring further.
How Webhooks Work
When an event occurs (booking created, cancelled, rescheduled, form submitted), meetergo sends an HTTP POST request to your configured endpoint with event details.Available Events
| Event | Trigger |
|---|---|
booking_created | New appointment is booked |
booking_cancelled | Appointment is cancelled (or attendee removed from group booking) |
booking_rescheduled | Appointment time is changed |
new_employee | New user is added to your company |
form_submission | Routing form or funnel is submitted |
Quick Setup
- Create a webhook endpoint on your server that accepts POST requests
- Register the endpoint via the API or dashboard
- Handle incoming events and return a 200 response
Example Endpoint (Node.js/Express)
Example Endpoint (Python/Flask)
Webhook Payload Structure
All webhook payloads include awebhookType field identifying the event, with the rest of the event-specific data at the top level:
Limits
| Limit | Value |
|---|---|
| Webhooks per company | 6 |
| Request timeout | 30 seconds |
| Payload size | ~100KB |
Best Practices
Return 200 quickly - Process webhooks asynchronously to avoid timeouts
Use HTTPS - Always use secure endpoints in production
Handle duplicates - Webhooks may be delivered more than once; use idempotent processing
Log everything - Keep webhook logs for debugging
Next Steps
Event Reference
Detailed payload documentation for each event
Managing Webhooks
Create, update, and delete webhooks via API