Event type
Keep Cal.com as the source of booking rules.
Choose the event type that owns the duration, availability, host routing, and booking constraints. Waaru uses that configuration rather than maintaining a second scheduling rule set.
Connect Cal.com and choose the event type for the journey.
Production setup still needs account authorization, field mapping, host-routing review, and one representative booking test.
Use the event type, availability rules, and required attendee fields your team already manages. The booking result remains part of the conversation so confirmation and follow-up do not start from zero.
In one line
Connect one Cal.com event type to show its available times, collect the required attendee details, create the booking, and use the confirmed result in the next workflow step.
Capability review updated .
Maintained by the Waaru product team. Read our editorial and product-claim review method.
No credit card. No commitment.
The selected event type determines the host, duration, availability, and attendee questions. The workflow carries that context through confirmation.
Cal.com
Choose the correct booking owner.
Operating boundary
The workspace authorizes its Cal.com account through OAuth and selects the event type used by the journey.
List event types and available slots, read one booking, or find bounded bookings for an attendee.
Create, reschedule, or cancel one booking through the reviewed booking actions.
Selected booking lifecycle events can continue confirmation, reminder, assignment, or handoff steps.
Authorize the account, choose the event type, map required attendee fields, review host routing, and test booking changes.
The journey does not replace Cal.com's event-type, host, availability, timezone, cancellation, or rescheduling rules.
Test a new booking, reschedule, cancellation, and the exception paths for the exact event type used in production.
Event type
Choose the event type that owns the duration, availability, host routing, and booking constraints. Waaru uses that configuration rather than maintaining a second scheduling rule set.
Customer journey
Ask the required attendee questions in the conversation or a WhatsApp Flow. Map only the fields the event type requires, then show available times and create the confirmed booking.
Follow-up
Carry the booking reference, time, event type, and outcome into confirmation, reminder, assignment, or team handoff steps. The customer does not need to repeat the appointment context.
Setup boundary
Availability, required fields, host routing, timezone handling, cancellation, and rescheduling rules can differ by event type and Cal.com account. Verify one representative new booking and one change before production traffic.
Yes. Connect an event type, collect its required attendee details, offer its available times, and create the confirmed booking from the journey.
Research notes
Primary Cal.com API reference for booking and event-type integrations.
Cal.com API v2 documents event-type, availability, and booking resources.
Cal.com API documentation · Accessed 13 August 2026
Ready to ship a WhatsApp flow that doesn't break?
Apply for founding access. No credit card. Cancel anytime.