Is there a native Zapier app?
No. Use Zapier’s, Make’s or n8n’s generic webhook trigger with the signed webhook; it carries the same booking data.
Signed webhooks for Zapier, Make and n8n
Send every booking, cancellation and reschedule from your WhenMeet.me booking link to any HTTPS endpoint — a Zapier, Make or n8n webhook trigger or your own server — as signed JSON.
What WhenMeet.me does with Webhooks (Zapier, Make, n8n)
- Events: booking.created, booking.cancelled and booking.rescheduled (plus a test event).
- Each delivery is a JSON POST with the x-whenmeet-event, x-whenmeet-delivery (a unique id for de-duplication) and x-whenmeet-signature headers.
- The signature is t=<unix seconds>,v1=<hex HMAC-SHA256 of "<t>.<body>"> with your secret, so receivers can verify it and reject replays.
- The signing secret is shown once when you create the webhook or rotate it.
- HTTPS only; redirects are not followed; 10-second timeout; a failed delivery is logged and not retried.
What happens when a meeting is booked, moved or cancelled
- Booked
- A booking.created delivery with the booking details.
- Rescheduled
- A booking.rescheduled delivery with the new time.
- Cancelled
- A booking.cancelled delivery.
How to set it up
- Create a webhook trigger in Zapier, Make or n8n (or expose your own HTTPS endpoint) and copy its URL.
- Sign in to WhenMeet.me, open /links and paste the URL next to Webhook.
- Save the signing secret shown once, and verify x-whenmeet-signature on your side.
- Use Send test to check the endpoint receives a delivery.
Webhooks (Zapier, Make, n8n) integration FAQ
Are failed deliveries retried?
No. A non-2xx response or timeout is logged in the activity list on /links. Use the delivery id to de-duplicate on your side.