Calendar & scheduling
AI Agents and Calendly
The only calendar integration in the product that needs no code at all: connect over OAuth, choose an event type, and the agent books while the caller is still on the line.
Where this stands today
Calendly is the exception on this whole site. Every other system here is reached through a webhook or a custom tool. Calendly has a first-class connector in the bitpull dashboard: an OAuth authorisation flow, a list of your event types pulled live from your account, and a stored selection of which event type the agent books into.
The connector exposes its own state - whether it is connected, whether it is configured, when it last synced, what the last sync error was, and when the OAuth grant expires. That last field matters more than it looks: an expired grant is the normal way this integration breaks, and it breaks quietly.
Because the agent books inside Calendly, everything Calendly already enforces still holds - buffers, minimum notice, daily caps, working hours, holidays. The agent cannot double-book, and it cannot book at 3 a.m. That is the reason to route booking through it rather than through a bespoke tool.
What the agent can do
OAuth connect from the dashboard
Connect returns an authorisation URL with an expiry. You approve in Calendly, and the connector reports itself connected without anyone touching an API key.
Event type selection
Your event types are read from the live account - name, slug, duration and whether the type is active - and the one you pick is what the agent offers.
Booking inside real availability
Availability, buffers and notice periods stay Calendly's job. The agent proposes what Calendly says is bookable.
Visible sync state
Last sync status, last error and OAuth expiry are exposed by the connector, so a broken grant is diagnosable rather than mysterious.
How it is wired
- ConnectOAuth authorisation URL
- Choose event typefrom your live account
- Caller asks for a slotphone, web or chat
- Agent booksinside Calendly rules
Limits worth knowing before you start
- Calendly is the only provider with a native connector. Google Calendar is set up with the bitpull team; Outlook and Cal.com are not connected at all.
- One configured event type per agent. Offering a 15-minute call and a 60-minute consultation means two agents, or a callback request and a human who decides.
- The OAuth grant expires. The connector reports the expiry - put a reminder against it, because a silently unbooked week is expensive.
- Rescheduling and cancelling by phone are not part of the connector. Both are a callback request today.
- What the caller hears when a slot has just been taken depends on the timing of the booking, not on the agent. Design the prompt to offer alternatives rather than to promise a specific time.
Questions
Does the agent double-book if two callers ask for the same slot?
Availability is enforced by Calendly, not by the agent, so the second booking fails the same way a second web visitor's would. Write the prompt so the agent offers an alternative instead of insisting on the slot it just proposed.
Can it book into Google Calendar instead?
Booking into a Google calendar runs in production, but it is set up with the bitpull team rather than through a self-serve button. See the Google Calendar page.
Can the caller cancel or move an appointment by phone?
Not through the connector. Treat it as a callback request: the agent takes the detail, the webhook delivers it, a human moves the booking.
Agents are created and operated on bitpull.ai - this site documents how to connect one. If the outbound webhook is not visible in your dashboard yet, that is the account capability flag, and support can enable it.