Cal.com bookings in a Notion database
Each Cal.com booking adds an item to a Notion database, ready for your meeting notes.
Cal.com → NotionCal.com handles the booking; everything around it still needs doing. Bizomate starts a workflow when a booking is made, cancelled or rescheduled or a meeting ends, and can find free slots and book them for a customer from any workflow. It works with cal.com and with a Cal.com you run yourself. Every run leaves a record of what it did.
| Label | Value |
|---|---|
| Plans | Every plan |
| Connect | An API key, on cal.com or your own address |
| Starts runs | Instantly |
| Kind | Connected app · Productivity |
Every event type, or one. The attendee's answers come as named fields. Set up with Cal.com when you publish.
Every event type, or one. Set up with Cal.com when you publish.
With the time it had before and the new one. Set up with Cal.com when you publish.
Sent at the booking's scheduled end, not when the call is left. Set up with Cal.com when you publish.
By status, dates, attendee email or event type; up to 1,000.
With a reason; Cal.com tells the attendees.
An event type's free times between two dates, each in UTC.
Books a slot for someone; Cal.com emails them the confirmation, as for a booking made on your page.
Yes. Choose Your own address and give the https address your Cal.com's API v2 answers on. It must be reachable from the public internet; an address on a private network is refused.
Yes. Get available slots finds an event type's free times between two dates, and Create a booking books one of them for the customer, who gets Cal.com's own confirmation email.
At the booking's scheduled end time, as Cal.com sends it — not when people leave the call. It suits follow-ups: a thank-you email, a row in a sheet, a task for the host.
No. Publishing a workflow with a Cal.com trigger adds the webhook for you, with its own secret, and every delivery is checked against it.
Each Cal.com booking adds an item to a Notion database, ready for your meeting notes.
Cal.com → Notion