Calendly integration

What it does

The Calendly integration lets your agency react the moment a client's calendar fills, and act on Calendly scheduled events without leaving TaskJuice. Connect a Calendly account once and your workflows can list and read scheduled events, cancel a booking, browse event types, look up an invitee, and listen in real time as invitees book, cancel, or no-show across every workspace you operate.

Connect a Calendly account

1. Open your workspace in TaskJuice and navigate to Connections.
2. Choose Calendly and click Connect.
3. Sign in to the Calendly account that owns the workspace you want to wire up and approve the requested access.
4. TaskJuice returns you to the workspace with the connection ready to use in any workflow.

To revoke access, open your Calendly account, navigate to Integrations and API, and remove the TaskJuice authorization. See the Calendly OAuth guide for the full grant flow.

Triggers

• calendly/invitee-created fires when an invitee books a Calendly scheduled event (invitee.created). The activation payload carries the event name, the originating user URI, and the full invitee object with questions and answers.
• calendly/invitee-canceled fires when an invitee cancels a booking (invitee.canceled). Use it to update CRMs, notify Slack, or kick off recovery sequences.
• calendly/invitee-no-show-created fires when an invitee is marked as a no-show on a scheduled event (invitee_no_show.created).

Every inbound POST is authenticated by recomputing HMAC-SHA256 over the concatenation of the signed timestamp, a literal period, and the raw request body, then comparing the hex digest against the value Calendly sends in the Calendly-Webhook-Signature header (formatted as t=<unix-ts>,v1=<hmac>). Activations that fail the signature or fall outside the replay window are rejected before they reach your workflow.

Actions

• calendly/get-current-user returns the currently authenticated Calendly user, including the user URI required by every list endpoint.
• calendly/list-scheduled-events lists scheduled events for a user URI with optional status and time filters, paginated by next_page_token.
• calendly/get-scheduled-event retrieves a single scheduled event by UUID.
• calendly/cancel-scheduled-event cancels a scheduled event with an optional reason shown to invitees.
• calendly/list-event-types lists event types owned by a user URI, paginated by next_page_token.
• calendly/get-event-invitee retrieves a single invitee on a scheduled event, including questions and answers.
• calendly/list-webhook-subscriptions lists webhook subscriptions scoped to an organization or user URI.

Known limitations

• Calendly enforces a per-token rate limit. When a 429 status is returned, TaskJuice surfaces it as a retryable error so the workflow can back off and retry.
• Webhook subscriptions are scoped to a single user or organization at creation time. To listen on multiple organizations, create one webhook (and one connection) per organization.
• Webhook signatures use a 5-minute replay window. Activations whose signed timestamp falls outside that window are rejected.
• The TaskJuice integration targets the Calendly v2 REST API. Fields surfaced only on private or beta endpoints are not exposed.