Calendly Webhook Setup Guide

Webhook subscriptions are available on paid Calendly plans (Standard or above). The connected user must be an owner or admin of the organization — Calendly rejects organization-scoped subscriptions from regular members with a permission error.

In the StackOne dashboard, open the Calendly connector profile and enable the webhook events you want delivered downstream. See the Available Webhook Events section below for the full list.

When webhook events are enabled (or the event selection changes), StackOne creates the webhook subscription on your behalf using the connected account’s credentials, registered for exactly the event types you enabled. You can inspect it with the connector’s list_webhooks action.

• For OAuth 2.0 connections, if the optional Webhook Signing Key setup field is filled in, StackOne registers it as the subscription’s signing key and Calendly signs each delivery with the Calendly-Webhook-Signature header (HMAC-SHA256).

Trigger a matching change in Calendly (for example, book a test meeting on one of your event types) and confirm the event reaches your downstream consumer.

• Calendly posts each event as a JSON payload; StackOne responds with 200 OK automatically.
• Calendly retries failed deliveries with exponential backoff and may disable subscriptions that keep failing.

Changing your event selection re-registers the StackOne-managed subscription. Disconnecting the account deletes it, stopping deliveries.

Events fired when invitees book, cancel, or are marked as no-shows on scheduled events.

• Invitee Created (invitee.created) — Fired when an invitee books a meeting
• Invitee Canceled (invitee.canceled) — Fired when an invitee cancels a booked meeting
• Invitee No Show Created (invitee_no_show.created) — Fired when an invitee is marked as a no-show
• Invitee No Show Deleted (invitee_no_show.deleted) — Fired when a no-show mark is removed

Events fired when meeting types are managed.

• Event Type Created (event_type.created) — Fired when a new event type is created
• Event Type Updated (event_type.updated) — Fired when an event type is modified
• Event Type Deleted (event_type.deleted) — Fired when an event type is deleted

Events on organization contacts. Requires a Calendly plan that includes contacts.

• Contact Created (contact.created) — Fired when a contact is created
• Contact Updated (contact.updated) — Fired when a contact is updated
• Contact Deleted (contact.deleted) — Fired when a contact is deleted

Events on routing form submissions. Only delivered on organization-scoped subscriptions (which is how StackOne subscribes).

• Routing Form Submission Created (routing_form_submission.created) — Fired when a routing form is submitted

Calendly delivers each event as an HTTP POST with a JSON body containing the event type in event (for example invitee.created), the delivery time in created_at, and the full resource under payload (the resource’s uri is used as the event ID).

When a signing key is registered, Calendly includes a Calendly-Webhook-Signature header in the form t=<timestamp>,v1=<HMAC-SHA256 signature> computed over the timestamp and raw body.