Calendly

Attify reads Calendly through its API, read-only, with OAuth or an API token, for sales meetings and bookings. It is the customer's own system, so what Attify reads there is connected data: the strongest provenance, and what a vendor verification rests on.

As a crm or calendar, for sales meetings, bookings

ItemCalendly
idthe invitee uri
started_atinvitee created_at
updated_atthe latest of the invitee's and the event's updated_at, the no-show's
and the cancellation's created_at (a mark may not move updated_at)
start, endevent start_time, end_time
statuscancelled: the invitee or the event is canceled; booked otherwise
cancelled_atcancellation.created_at (the invitee's, else the event's)
cancelled_bycancellation.canceler_type: invitee is "invitee", host is "host"
rescheduled_*old_invitee / new_invitee (invitee uris, so item ids)
created_byapp: scheduling_method api; user: invitee_scheduled_by (that user's
uri); invitee otherwise, id the event type (the booking link used)
changesthe cancellation, by "invitee" or "user" (host), fields start when it was
a reschedule (rescheduled), else status
ainull: Calendly does not say
attendancemark, no_show when no_show is set; by_app false (who marked it is not
recorded)
service, titleevent name (the event type's name)
duration_minutesend minus start
price, currencyinvitee payment.amount, payment.currency
provider,the first event membership's user_email (the host)
organizer
attendeesthe invitee, accepted
locationevent location.location, else its type
linkscalendly:<event uri>; google:<id> when the event's calendar_event
is a Google one (unverified field)