Yes. Krokul CRM integrates with Calendly. When someone books through your Calendly link, Krokul finds or creates the contact, opens or updates the deal and puts a meeting task on the booked time for the host. A reschedule moves the task, a cancellation closes it, and a no-show is marked on the deal. These flows run through the Krokul app in Zapier, Make, n8n or Albato, or through the Krokul API and webhooks.
Automation platformsZapierMaken8nAlbato
Calendly sends invitee.created when someone books. Krokul finds the invitee by email or creates the contact, opens a deal in the pipeline chosen for that event type and adds a meeting task at the event start, assigned to the Krokul user who hosts it. The Calendly invitee URI stays on the deal as an external key.
Questions on the Calendly booking page, such as company size or the product of interest, come with the invitee. Krokul writes them to the deal as a note, so the manager reads them before the call and does not ask twice.
When an invitee reschedules, Calendly sends invitee.canceled and a new invitee.created. Krokul treats the pair as one change and moves the existing task to the new time. A plain cancellation cancels the task and adds the reason from Calendly to the deal feed.
When the host marks a no-show in Calendly, invitee_no_show.created reaches Krokul. The meeting task gets the result No-show, and an automation rule can move the deal to a stage such as "Reschedule needed".
The manager clicks Scheduling link on a deal. Krokul creates a single-use Calendly link for the chosen event type and puts it into the reply box, so the customer books a slot that belongs to this deal.
| Calendly | Direction | Krokul | When |
|---|---|---|---|
Invitee (invitee.created) | Calendly → Krokul | Contact, deal and meeting task | On booking |
| Questions and answers of the booking | Calendly → Krokul | Note on the deal | On booking |
Reschedule (invitee.canceled + invitee.created) | Calendly → Krokul | New time of the same task | When the invitee picks another slot |
Cancellation (invitee.canceled) | Calendly → Krokul | Task cancelled, reason on the deal | When the invitee or the host cancels |
No-show (invitee_no_show.created) | Calendly → Krokul | Task result and deal stage | When the host marks a no-show |
| Routing form submission | Calendly → Krokul | Contact and deal | routing_form_submission.created |
| Single-use scheduling link | Krokul → Calendly | Link offered on the deal | When the manager asks for a link |
Yes. Krokul integrates with Calendly through the Krokul app in Zapier, Make, n8n and Albato, and through its API and webhooks. Bookings create contacts, deals and meeting tasks, and reschedules, cancellations and no-shows update them.
Calendly lists webhooks for the Professional, Standard, Standard Plus, Teams, Teams Plus and Enterprise plans. Access can also depend on when the account was created and on add-ons.
Calendly sends a cancellation and a new booking. Krokul reads them as one change and moves the existing task instead of closing it and opening a second one.
No. Krokul finds the contact by email and adds the new meeting task to the open deal of that contact.
Calendly keeps the scheduling. Availability, event types, booking pages and reminders live there. Calendly offers webhooks on its paid plans, so the account that connects needs one of them.
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.
Calendly is a trademark of Calendly LLC. Krokul is not affiliated with Calendly.