This workflow is especially suitable for founders and operators offering services to their clients and regularly scheduling sales or project update meetings.
How it works
When a booking is created, rescheduled, or canceled in cal.com, this workflow syncs the meeting and contact data into Notion.
When a new booking is scheduled:
-
Creates a meeting in the dedicated Notion database. Here we can customize all the information to include on the meeting page (e.g., mapping the answers to custom questions).
-
Finds the Contact(s) in the dedicated Notion database (based on the email). If the Contact(s) exists, it links the contact(s) to the newly created meeting. If the Contact(s) doesn’t exist, it creates the contact(s) and links them to the newly created meeting.
When a booking is rescheduled:
-
The automation finds the event in Notion (based on the “cal id” property)
-
It updates the event date and time in Notion
When a booking is cancelled:
The automation deletes the event in Notion (i.e., it archives the page, which remains available in the Trash for 30 days)
Requirements
A Cal account and API key.
A Notion account and connection with access to all the databases involved (Meetings, Contacts). Find all your connections, manage their access, or create a new connection on your Notion Integrations page.
A Meetings and Contacts database in Notion, both accessible by the Integration (see step 2 above). The database names don't matter. You will input your database IDs in the workflow. Find a Notion database ID in the URL between the slash characters.
Notion database column specifications
In the Meetings database, these are required properties:
- Event time (date)
- cal id (text)
- Contacts (relation)
- Name
In the Contacts database, these are required properties:
- Name
- Meetings (relation)
Read the essay and watch the video for a detailed walkthrough.