The Temporal Grid
Read as MarkdownEvery Cronofy capability is built on the Temporal Grid. Your application connects to it once, and each capability you add uses that same connection.
Description
- Managed scheduling and rescheduling groups Scheduling and Scheduling Controls.
- Modular calendar and availability control groups Availability, Calendar Events, and UI Elements.
- Meeting conferencing and transcription groups Conferencing and Meeting Transcripts.
- All three pillars are built on the Temporal Grid, which covers applications, Organizational Units, data centers, webhooks, and the MCP Server.
The capabilities on top are grouped into three pillars:
- Managed scheduling and rescheduling
- Meeting conferencing and transcription
- Modular calendar and availability control
Use them independently or together.
Each pillar has its own Authorization page saying which ways of obtaining access suit it. Connectivity explains the ways of obtaining access, and how to choose between them. How Cronofy connects to your users’ calendar and conferencing services is covered in Connect with Cronofy.
In this section
Integration approaches
Choosing how to connect to Cronofy, depending on whether you're building for your own company's workflows or for your customers through your product.
Connectivity
How your application gets access to calendars and scheduling: at the organization, service account, or user level.
MCP Server
MCP Server for interacting with the Cronofy service from an MCP Client. Typically with an agentic workflow tool.
Real-time scheduling
How Cronofy books meetings against live calendars and the availability people have approved in advance, and keeps them right as plans change.
Webhooks & workflows
The webhooks Cronofy sends through a meeting's lifecycle, so your application stays up to date and can drive its own workflows.
Data centers
Cronofy currently provides six data centers. One in the USA, the default, and others in Australia, Canada, Germany, Singapore and the United Kingdom. They are run as completely separate instances with no data flow between. This allows you to ensure data is kept within jurisdictional boundaries, eg. the EEA.