Yes. Krokul CRM integrates with Cal.com. A new Cal.com booking finds or creates the contact, opens or updates the deal and places a meeting task on the booked slot for the host. Reschedules move that task, cancellations close it, and a no-show or a finished meeting is recorded on the deal. The flows run through the Krokul app in Zapier, Make, n8n or Albato, or through the Krokul API and webhooks.
Automation platformsZapierMaken8nAlbato
Cal.com sends BOOKING_CREATED the moment someone picks a slot. Krokul matches the attendee by email or adds a new contact, then opens a deal in the pipeline mapped to that event type and puts a meeting task at the start time for the host. The booking UID becomes an external key. Later events find the same deal.
Answers from the booking form, such as company name or team size, travel in the responses of the payload. Krokul writes them to the deal as a comment. The manager reads them before the call.
On BOOKING_RESCHEDULED Krokul moves the existing meeting task to the new time. A BOOKING_CANCELLED event closes the task as cancelled and writes the reason into the deal feed.
When a host marks an attendee absent, BOOKING_NO_SHOW_UPDATED sets the task result to no-show, and an automation rule can move the deal to a follow-up stage. After a Cal Video call, MEETING_ENDED closes the task as done, and the recording link from RECORDING_READY joins it.
A Cal.com Routing Form sends FORM_SUBMITTED even when the visitor leaves before booking. Krokul creates the contact and the deal from it, so the inquiry still reaches a manager.
| Cal.com | Direction | Krokul | When |
|---|---|---|---|
Booking (BOOKING_CREATED) | Cal.com → Krokul | Contact, deal and meeting task | An attendee books a slot |
Booking (BOOKING_RESCHEDULED) | Cal.com → Krokul | New time of the same task | The attendee or host picks another time |
Booking (BOOKING_CANCELLED) | Cal.com → Krokul | Task cancelled, reason in the deal feed | The booking is cancelled |
No-show (BOOKING_NO_SHOW_UPDATED) | Cal.com → Krokul | Task result and deal stage | The host marks an absence |
Meeting (MEETING_ENDED, RECORDING_READY) | Cal.com → Krokul | Task done, recording link on the task | A Cal Video meeting ends |
Routing Form (FORM_SUBMITTED) | Cal.com → Krokul | Contact and deal | A visitor submits the form |
| Booking cancel or reschedule through the API | Krokul → Cal.com | Task cancelled or moved in Krokul | A manager changes the meeting from the deal |
Yes. Krokul integrates with Cal.com through the Krokul app in Zapier, Make, n8n and Albato, and through its API and webhooks. Bookings become contacts, deals and meeting tasks.
Booking created, rescheduled and cancelled, no-show updated, meeting ended, recording ready and form submitted. Each one updates the deal or the meeting task it belongs to.
No. Cal.com sends a separate reschedule event, and Krokul moves the time of the task it already created for that booking.
Yes. Cal.com API v2 cancels a booking with a POST to the cancel endpoint of its UID, and Krokul calls it when the manager cancels the meeting task.
Cal.com keeps the scheduling side. Event types, availability, booking pages, Routing Forms and Cal Video live there. The Cal.com API key allows 120 requests per minute by default, so bulk backfills of old bookings run in batches.
Tell us which service you use and what should move between it and Krokul. We reply with the way to do it and when it will be ready.
Request received. We reply to your email.
Cal.com is a trademark of Cal.com, Inc. Krokul is not affiliated with Cal.com.