How to Connect an AI Agent to Calendly or Cal.com to Book Meetings

An AI agent can work with Calendly or Cal.com in two ways: send the lead a booking link, or book the meeting directly in the conversation through the platform's API. Direct booking converts better because the lead never leaves the chat, but the two platforms differ in what their APIs allow and which plans you need.

I built the Calendly, Cal.com, Google Calendar and Microsoft 365 integrations in ReplySetter, so I've spent a lot of time in these APIs. Here's what you need to know.

Booking links vs direct booking

Sending a link

The AI sends your Calendly or Cal.com link at the right moment.

• Pros: works on any plan, simple.
• Cons: the lead has to leave the conversation, pick a time and fill in a form. Every extra step loses people.

Make links better: pre-fill the lead's name and email so the form is quicker, and use single-use links so each lead gets their own.

Direct booking

The AI checks availability through the API, offers two specific times in the chat, and books the one the lead picks.

• Pros: fewer steps, feels like talking to a person, higher completion.
• Cons: needs API access, and on Calendly a paid plan.

In my experience, offering two times in the chat ("Tuesday at 2pm or Wednesday at 10am?") converts noticeably better than "here's my link".

Calendly: what to know

• Booking through the API requires a paid Calendly plan (Standard and above). On the free plan, an AI agent can still send booking links.
• Webhooks (booked, cancelled) also need a paid plan.
• There's no direct reschedule API call, so an agent reschedules by booking the new time first, then cancelling the old one, so the lead is never left without a booking.
• Single-use links are available, useful for sending each lead a personal link.

More on the Calendly AI agent page.

Cal.com: what to know

• The API works on any plan, including free, and self-hosted Cal.com works too.
• Event types of all kinds (personal, team, round-robin, collective) can be booked.
• Webhooks for booked, rescheduled, cancelled and no-show events.
• Required booking questions on the event type can be asked in the conversation and sent with the booking.
• Pre-filled links with the lead's name and email.

More on the Cal.com AI agent page.

Google Calendar and Microsoft 365 as alternatives

If you don't use a scheduling tool, an AI agent can book straight into Google Calendar or Outlook:

• open times come from the calendar's free/busy plus the working hours you set,
• the lead gets a calendar invitation with a Meet or Teams link,
• cancellations, declines and moves made on the calendar are picked up.

This is often the simplest option for a solo business owner.

Setting it up in ReplySetter

1. Connect the calendar: sign in with Cal.com or Calendly (or paste an API key), or sign in with Google or Microsoft.
2. Your event types appear in the agent builder. For Google and Microsoft, set up the meetings agents can book: length, buffer, working hours, notice.
3. Tag calendars in step instructions to choose which one to book when: "If they have 10+ seats, book @Calendar.Product demo, otherwise @Calendar.Intro call".
4. Add always-invite guests, like a sales manager.
5. Pick booking behaviour: book directly, or send a link.
6. Turn on no-show and cancellation recovery so the agent offers new times.
7. Test in the sandbox, which can simulate bookings without touching your real calendar.

See calendar booking for the full feature list.

What happens after booking

A good AI agent keeps going after the booking:

• Confirmation with time, timezone and video link.
• Bookings made on the page (when the lead used the link) are picked up by webhook, so the conversation knows and follow-ups stop.
• Cancellations and no-shows trigger recovery messages with new times.
• Reporting: bookings, cancellations, no-shows and show rate per agent, calendar and step.

Common issues and fixes

• Timezone confusion: the agent should always state the timezone or use the lead's local time.
• Double booking: direct booking through the API checks availability at the moment of booking, which avoids most of it.
• Wrong event type: tag calendars explicitly in the instructions for each situation.
• Booking forms with required questions: make sure the agent asks them, or the booking will fail.