Calendly
Connect your customers' Calendly accounts so your product can read scheduled events, track booking activity, and react to new meetings without any polling on your side. A personal access token is all the customer needs to provide.
What you can do
List all scheduled events for any event type
Read past and upcoming events across the customer's Calendly account, filtered by date range, status, or event type UUID. Covers one-on-ones, round robins, and collective events.
Read invitee details per event
Fetch name, email, timezone, and custom question answers for each invitee on a scheduled event. Useful for pre-populating CRM records or triggering onboarding flows.
Detect cancellations and rescheduling
Query events by status to find cancellations or events that have been rescheduled, so your product can update downstream systems without waiting for a webhook.
Read event type configuration
Pull the list of event types the customer has set up, including duration, name, slug, and booking URL. Lets your product surface the right link at the right step in an onboarding flow.
Fetch user and org membership info
Read the authenticated user's profile and org membership, covering name, email, and organisation URI, so your product can scope requests correctly for multi-user Calendly accounts.
Track no-shows and routing form responses
Read no-show flags on invitees and pull responses from Calendly routing forms when customers use them to qualify leads before a meeting is booked.
Triggering onboarding steps when a kickoff call is booked
You sell a B2B project management tool. When a new customer, Harborview Consulting, signs a contract, your onboarding flow needs to know the moment their team books a kickoff call so it can auto-assign tasks and send a pre-meeting checklist. Harborview uses Calendly for all external scheduling.
- 1
Customer provides a token
Harborview's admin opens Calendly, goes to Integrations and API and Webhooks, generates a personal access token, and pastes it into your product's connection form. Askel validates the token with a call to the /users/me endpoint.
- 2
Discover event types
Askel reads Harborview's event types. Your onboarding flow shows the list and asks the admin to mark which event type is the kickoff call. The event type UUID is stored against the customer record.
- 3
Poll for new bookings
Askel queries the /scheduled_events endpoint filtered by the kickoff event type and a start_time after today. Your product checks for new events on a schedule and surfaces any it has not seen before.
- 4
Extract invitee data
When a new event appears, Askel fetches the invitee list for that event URI. Your product reads name and email, creates a contact record, and assigns the pre-meeting task checklist.
- 5
Mark onboarding milestone complete
Your product marks the kickoff-call-booked milestone in the customer's onboarding timeline and sends the pre-meeting checklist to the invitee email. No manual step is required from your team.
API token
The customer generates a personal access token from calendly.com under Integrations and API and Webhooks. They paste it into Askel once. Askel sends it as a Bearer token on every request to api.calendly.com; the token never reaches your servers.
How Askel sits between your product and the customer's system
FAQ for Calendly
Does this require a paid Calendly plan?+
Can we receive real-time booking notifications instead of polling?+
What happens if the customer revokes or rotates the token?+
Can we read events across multiple users in the same Calendly org?+
catching drift before it breaks, and hitting go-live dates.
© 2025 Askel.ai. All rights reserved.