Skip to content
AskVault Docs
Try Free →

How to connect Calendly to AskVault

Written by , Founder, AskVault · Reviewed by Aashiq
Last updated: · 3 min read

What this integration unlocks

The demo_scheduler skill becomes available. When a visitor shows demo intent ("can I see a demo?", "I want to schedule a call", "let's book a meeting"), the bot:

  1. Asks for their name, email, and what they want to discuss.
  2. Pulls live availability from your Calendly event type.
  3. Offers 3 suggested slots.
  4. The visitor picks one; the bot books it.
  5. Confirmation emails go from Calendly to both you and the visitor.

End-to-end booking in 30 to 90 seconds. The skill is on Growth and above. Growth+

Setup

Three minutes end-to-end.

  1. In AskVault, open AI Agents > Skills > demo_scheduler. Click Enable.
  2. Click Connect Calendly. OAuth consent screen opens.
  3. Sign in to Calendly. Approve the requested scopes (read scheduling URLs, write invitee creations).
  4. Pick the event type. AskVault lists your active event types (Discovery Call, Product Demo, Office Hours, etc.). Pick which one the bot should book.
  5. You're redirected back to AskVault. Connection shows active.

Test by opening your widget and saying "I'd like a demo". Bot should offer time slots within a few seconds.

Multi-event-type routing

Want the bot to pick different event types based on visitor profile? Configure routing under AI Agents > Skills > demo_scheduler > Routing:

  • Default event type. What gets offered by default.
  • Routing rules. Conditions that switch to a different event type. Example: visitor mentions "enterprise" or "100+ users" routes to the 45-minute "Enterprise Discovery" event instead of the 15-minute "Quick Demo".

Rules are evaluated in order. Most teams start with one default event type and add rules later.

What gets passed to Calendly

When the bot books a slot, AskVault sends these fields to Calendly's invitee creation API:

  • Name. From the visitor (or from identity verification if enabled).
  • Email. Same.
  • Question/Note. A summary of the conversation so the sales rep knows context before the call.

Your Calendly event type's custom questions get pre-filled where possible. If a question requires a specific format, AskVault tries to extract it from the conversation; otherwise it asks the visitor.

Round-robin distribution

If your Calendly event is configured as a round-robin (Calendly Teams or Enterprise feature), the booked slot rotates among your team automatically. AskVault doesn't override this; it just passes the booking request and Calendly handles the rotation.

For teams without Calendly round-robin, AskVault can simulate it by rotating between event types under Routing > Rotation.

Calendar invite content

Calendly sends the calendar invite. AskVault doesn't customize the invite directly. To customize the invite content:

  1. In Calendly, open Event Types > [your event] > Notifications.
  2. Edit the invite-to-invitee template.
  3. Save.

The customization persists across all AskVault-booked slots.

Limits

  • Calendly API rate limits. 100 requests per minute per token. AskVault stays well under this for normal traffic.
  • Booking latency. About 800 to 1,500 ms end-to-end including Calendly API roundtrips. The customer sees the bot "typing" briefly before confirmation.
  • Time zone handling. Calendly auto-detects the visitor's timezone from their browser. The bot shows slots in their local time.

Common pitfalls

No slots offered. Your Calendly event has no availability for the next 7 days. Adjust availability in Calendly or extend the search window under demo_scheduler > Search Window.

Booking fails with "invitee already exists". The same email already has a future booking for this event type. Calendly's duplicate-booking protection. Bot offers to reschedule the existing one instead.

Wrong event type offered. Routing rules aren't firing as expected. Test rules under Routing > Test Mode with sample visitor profiles.

Bot books slots in wrong timezone. Visitor's browser sent UTC instead of their local zone. Identity verification fixes this; verified visitors carry their timezone explicitly.

FAQ

Does this work with Calendly Free?

Yes. The integration uses standard Calendly OAuth APIs that work on every Calendly plan. Round-robin and team scheduling require Calendly Teams or Enterprise.

Can the bot reschedule an existing booking?

Yes. If the visitor's email matches a future booking, the bot can offer to reschedule rather than create a duplicate.

Can the bot cancel a booking?

Yes, with explicit consent from the visitor. "Yes, please cancel my Tuesday 3pm slot" triggers the cancellation flow.

Does this work with Cal.com or other scheduling tools?

Not natively. Calendly is the only scheduling tool with a first-party integration. For Cal.com, SavvyCal, or other tools, use the custom_webhook skill to call your scheduling API directly.

No. The integration uses your existing event types without modifying them. Visitors who arrive via your direct Calendly link see the same experience they always did.

Was this page helpful?