Calendly
Booked is a signal. Attended is the conversion. You choose.
Calendly webhooks report the invitee lifecycle. Apointo turns invitee.created into appointment_booked, tracks cancellations, and lets attended meetings, not raw bookings, feed the ad platforms if you want it that way.
Pages marked Planned are complete specifications written before the connector ships. They validate demand. Connectors with real delivery logs are marked Production or Beta.
Every booked meeting looks like a good one
Bidding on booked meetings pays for no-shows. The meeting that matters is the one where both people showed up, and Calendly alone cannot tell your ad account which was which.
The lifecycle becomes distinct events
Booking, cancellation, and attendance each carry their own event name. You decide which one becomes the advertising conversion, per destination, and changing your mind does not require rebuilding the flow.
- 01Ad click lands on the scheduling page
- 02UTM and click ids captured at booking
- 03invitee.created webhook reaches Apointo
- 04No-shows and cancellations update the record
- 05Completed appointments become the conversion
Subscribe the invitee.created and invitee.canceled webhooks.
Capture utm parameters and click ids at scheduling time.
Choose which lifecycle state becomes the conversion.
Cancellations follow your retraction rule automatically.
| From | Apointo |
|---|---|
| invitee.created | appointment_booked |
| Marked attended (via your workflow) | appointment_attended |
| invitee.canceled | appointment_cancelled (retracts booked signal) |
How do no-shows get reported?
Attendance status comes from your workflow update. When your system marks the invitee a no-show, Apointo applies the retraction or correction you configured.
Can different destinations use different events?
Yes. One destination can optimize on bookings while another waits for attended meetings.
When does this connector ship?
This page is the working specification. Join the early-access list and build order follows demand.