Calendly to Chromoly: Track Bookings and Reschedules
Keep scheduling events linked to the correct lead or project. Model cancellation and rescheduling separately from attendance or a completed meeting.
Before connecting
This is an integration design guide, not a claim that a ready-made connector is enabled in every app. First check the connection settings available in your app. If the required receiver, authentication or action is missing, scope that implementation with Chromoly before sending production events. Chromoly does not offer a public REST API.
Provider requirements
Calendly documents invitee.created and invitee.canceled webhook subscriptions. A reschedule generates both types, so it should not be treated as two unrelated meetings.
Official sources: Webhook subscriptions · Rescheduled-event payloads.
Implementation outline
- Confirm webhook access, account permissions and the intended user or organization scope in Calendly.
- Create a meeting record keyed by provider references and store the event time and time zone.
- Handle creation, cancellation and linked reschedules without losing the previous meeting reference.
- Match a contact carefully; a shared or changed email address should not silently merge unrelated clients.
Example workflow
A demo booking can create a preparation task for the assigned salesperson. A reschedule should update the active meeting and its task rather than leaving both dates as upcoming. Record attendance separately after the meeting.
Test the full delivery path
- Send a fictional event to a test destination and verify the resulting record, not only an HTTP response.
- Replay the same event and confirm it does not repeat a business action.
- Try an invalid credential or signature, a missing field and a temporary failure.
- Check both the provider’s delivery history and the app’s workflow history. Define who investigates missing events.
Frequently asked questions
Does a booking event prove the meeting happened?
No. A booking records a scheduled event. Track attendance or completion separately if your reporting needs it.
Is this a one-click native connector?
This page describes a connection pattern. Use only integration settings and actions actually exposed by your app, or agree the missing implementation with Chromoly before rollout.
Related reading
- Build a Booking Portal with AI
- Build a Custom CRM with AI
- Chromoly Integrations: Connections, Setup and Testing
Custom builds open on December 1, 2026. Self-service opens in January 2027. Check current availability and limits before planning a rollout.
Discuss your system with us.
Bring your workflow and requirements. We can scope a Managed build and ongoing service around them.
Book a discovery call