Integration approaches

How you connect to Cronofy depends first on whose workflows you’re building for: your customers’ through your product, or your own company’s.

Authorization & Authentication explains the applications, Organizational Units, and accounts every approach is built from, and Permissions how Cronofy decides what your application can do with users’ calendars.

Your customers’ workflows, through your product #

If you’re building a product that your customers use to schedule, each customer connects their own calendars and configuration to your application.

Managed scheduling and rescheduling Recommended

Use a Managed Organizational Unit for each customer, authorized with Organization Connect. Your application gets the customer’s members, their calendars, and their scheduling configuration, such as Selection Rules and Templates, so Cronofy can facilitate each meeting’s workflow from finding a time through rescheduling and cancelling.

This works for customers of any size. The customer’s members connect their calendars behind the scenes, either through a service account their administrator authorizes once, as with Enterprise Connect, or each for themselves, as with Individual Connect. Your application doesn’t need to handle either; it works with the Organizational Unit.

• Create Scheduling Requests for the Organizational Unit as a whole, letting Cronofy choose the host.
• Drop to an individual member when you need to, by passing their sub in the Cronofy-Impersonate header alongside the Organizational Unit’s access token.

Getting Started walks through this approach with a Sandbox.

Calendar and availability only #

If you only need the calendar and availability level, such as reading and writing events or querying availability in your own scheduling flows, you can connect to calendars directly instead:

• Enterprise Connect connects a customer’s whole organization through a service account their administrator authorizes once.
• Individual Connect connects each person, who authorizes your application for their own calendars.

Your application then works with modular calendar and availability control, and builds the scheduling workflow itself.

Your own company’s workflows #

If you’re building for people inside your own company, such as an internal recruiting tool or CRM, use an Internal Application.

An Internal Application is linked to your company’s Organizational Unit, and has access to all of its members without any authorization flow.

• Authenticate with the application’s client_secret.
• Act as a particular member by passing their sub in the Cronofy-Impersonate header.

An Internal Application can only access one Organizational Unit, so it isn’t suitable for a product your customers use.