INTEGRATION
Scheduling actions
Meeting scheduling and booking platforms
- Actions
- 72
- Services
- 3
- Maintained by
- Flomation
Services
Acuity actions
- Acuity: Book AppointmentBook a new Acuity appointment for a client at a given date and time.
- Acuity: Cancel AppointmentCancel an Acuity appointment, optionally with a note.
- Acuity: Check Time AvailabilityValidate whether a specific date/time is bookable for an Acuity appointment type before booking it.
- Acuity: Create ClientAdd a new client to your Acuity address book.
- Acuity: Delete ClientRemove a client from your Acuity address book. The client is identified by first name, last name and phone.
- Acuity: Get AccountRetrieve the authenticated Acuity account profile (name, email, timezone, currency).
Cal.com actions
- Cal.com: Add Team MemberAdd a user to a Cal.com team as a member, admin or owner.
- Cal.com: Cancel BookingCancel a Cal.com booking, optionally with a reason.
- Cal.com: Confirm BookingConfirm a Cal.com booking that requires confirmation.
- Cal.com: Create BookingBook a Cal.com event type for an attendee at a given start time.
- Cal.com: Create Event TypeCreate a new Cal.com event type (a bookable meeting slot definition).
- Cal.com: Create ScheduleCreate a Cal.com availability schedule defining the hours you can be booked.
Calendly actions
- Calendly: Cancel EventCancel a scheduled Calendly event (booking), optionally with a reason shown to the invitee.
- Calendly: Create Scheduling LinkCreate a single-use scheduling link for an event type: the link expires after one booking.
- Calendly: Get Availability SchedulesList a Calendly user's availability schedules (working hours). Defaults to the connected user.
- Calendly: Get Busy TimesList a Calendly user's busy periods (internal and external calendar events) within a date range of up to 7 days.
- Calendly: Get Current UserRetrieve the Calendly user the connection belongs to, including their scheduling URL and organisation.
- Calendly: Get EventRetrieve a single scheduled Calendly event (booking) by its ID or URI.
Wire Scheduling into the rest of your stack
Every action here drops onto the canvas alongside the other 3,585, so a Scheduling step can sit between a form, a database and a message without any glue code.
