Botpress Calendly Integration: How a Website Bot Books Calls

Coding Liquids tutorial cover featuring Sagnik Bhattacharya for Botpress Calendly Integration: How a Website Bot Books Calls.
Coding Liquids tutorial cover featuring Sagnik Bhattacharya for Botpress Calendly Integration: How a Website Bot Books Calls.

Install Botpress's official Calendly integration, paste in a Calendly personal access token, then place its Schedule Calendly Event card after your qualifying questions. The card creates a one-time booking link for your chosen event type; the visitor picks a time on Calendly's page, and the integration's Event Scheduled trigger tells the bot the booking happened.

The Complete Excel Course with AI Integration

From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.

By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner

Buy now

The bot never sees or offers free times itself. Neither Botpress's integration page nor the integration's published source code includes an availability lookup, so slot choice stays on Calendly's page. A plain copied event link also works, with no token at all, but then the bot cannot tell whether anyone booked, and a visitor typing “done” is not confirmation.

What should the Botpress bot do, and what should Calendly do?

In a Botpress booking bot, the bot identifies the topic, explains what the call covers and provides the booking link, while Calendly owns available times, the final booking form and its confirmation. For an illustrative furniture maker, the first task is to arrange a 20-minute standard-product discussion. The bot does not quote bespoke work or promise that a production slot is reserved.

Botpress's Calendly page says the bot can schedule events and respond when events are scheduled, cancelled or when an invitee does not show up. The integration's source code, which the Botpress team maintains in its public repository, shows what “schedule” means in practice: its one action, Schedule Calendly Event, “generates a link for scheduling an event”. It creates a single-use scheduling link for the event type you name and tags that link with the chat's conversation ID. Its four triggers cover a booking, a cancellation, and a no-show being marked or unmarked.

RouteCustomer finishes bookingWhat the owner must verify
Plain event link in a bot messageOn Calendly's booking pageCorrect event and usable times; the bot never learns the outcome
Integration's single-use linkOn Calendly's booking pageEvent owned by the token's user, trigger firing, booking matched to the right chat
Direct API bookingInside a custom-built chat flowAvailable times, permissions, rate limits, failed requests and duplicates

Start with the plain link when one event and one host answer the business need: it has the fewest moving parts and lets the owner test the scheduling rules without credentials. Move to the integration's single-use link when you need the bot, or a later automation, to know which chats turned into bookings. Direct conversational booking is a separate, custom implementation, not a necessary first step.

The beginner Botpress FAQ tutorial covers the basic bot and source setup. If the goal is to check a calendar and create an appointment directly, compare the Google Calendar booking workflow before choosing the architecture. Keep one scheduling system responsible for the final reservation.

How do you set up a Calendly event a visitor can actually book?

Create or select a one-on-one event in Calendly and copy its event-specific scheduling link, because that is the link a fresh visitor can actually book. The current Scheduling help page describes + Create for creating an event type and Copy link on its card for the event-specific scheduling page. Use that link rather than an administrative page address or the landing page that lists all your meetings. If you will use the integration, create the event under the same Calendly user whose token you will paste: the action looks the link up among that user's own event types and stops with “Event type not found” if it belongs to someone else.

Set the discussion duration, available hours and connected calendar deliberately. Calendly's help page describes connecting calendars through Settings → Scheduling → Calendars. It checks connected calendars for busy times and adds new meetings to the calendar. Confirm the connected account belongs to the person taking these calls; a correct event description does not compensate for checking the wrong diary.

For the furniture illustration, assume a two-hour afternoon window and a proposed 20-minute discussion plus ten minutes of preparation between calls. That suggests four 30-minute planning blocks in 120 minutes. This is an illustrative capacity calculation, not a guarantee that four slots will appear: existing calendar events, notice rules, buffers and the event settings determine what Calendly actually offers.

Open the copied link in a fresh browser session. Check that the event title, duration and host match the intended service. Calendly says invitees do not need an account to book. If the link asks the customer to log into an administrative area, revisit the copied address before changing Botpress. A bot cannot repair a link that leads to the wrong surface.

Add an illustrative busy event covering the middle of the test window in the relevant connected calendar. Reopen the booking page and confirm that conflicting times are unavailable. If the slot remains visible, inspect the calendar connection and busy-time settings. Do this before sending the link to visitors, because a booking bot should not become the first test of your diary configuration.

How should the bot qualify a visitor without repeating a form?

A booking bot should qualify a visitor with short questions that matter for routing, not a repeat of the booking form. For the furniture maker, ask whether the visitor wants a standard product or a fitted item, then whether they want to discuss measurements or finishes. The first answer determines whether the standard-product call is appropriate. The second prepares the visitor, without requiring the bot to store a detailed design brief.

Studio's Capture Information cards support structured inputs such as Single Choice and store the result in a workflow variable, a named value used later in the conversation. Create one card for the service category and another only if a second answer changes the next step. Give the variables clear names in your own worksheet, such as service category and discussion topic. In each card's advanced settings, set the number of retries to one or two with a retry message such as “Please choose one of the buttons”, and switch on Add transition to handle failure, so an unclear answer goes to your enquiry route instead of looping.

Illustrative conversation specification:
Opening: "I can help you find the right product discussion."
Question 1: "Standard shelf or fitted furniture?"
Standard shelf: ask "Measurements or finishes?"
Then: explain the 20-minute discussion and send the approved event link.
Fitted furniture: explain that staff must review the project first.
Do not offer a standard-product booking as a fitted-design assessment.
Do not collect payment details or confirm a production date.

A sample successful exchange is: visitor chooses standard shelf, then finishes; bot replies, “Use this link to choose a time for a 20-minute standard-product discussion. Have your preferred finish and approximate dimensions ready. Your booking is complete when Calendly confirms it.” The wording gives a clear action without implying a slot has already been held.

A garage would use a different illustrative question: “Do you want a call about a service estimate or to arrange a vehicle inspection?” The estimate call can use its own approved event link, while an inspection request needs the garage's existing booking process. Do not turn a call appointment into a promise that workshop space, equipment and a technician are all available.

Let the scheduling page collect the contact information it needs. Asking for the same name and address in chat first creates repetition unless you have designed and verified a supported transfer. Avoid putting personal details into link parameters as an improvised shortcut. A short classification question can be useful without requiring an owner to build a customer-data pipeline.

If you want help fitting a booking bot into how your business actually takes enquiries, I offer one-to-one AI consultations for small businesses.

What should the handoff message say about availability?

The handoff message should send the booking link and say that the booking page shows available times. The bot should never offer guessed time slots.

On the plain-link route, put the approved event link in a Text card on the intended branch. On the integration route, add the Schedule Calendly Event card to that branch instead: its Event Type URL field takes the event's scheduling link, its Conversation ID field takes the current conversation's ID (the card's placeholder suggests event.conversationId), and its output, the Scheduling Link URL, goes into the next message. If an Autonomous Node writes that message, remember that it cannot read variables until you add them under its Variables setting, and instruct it never to invent a booking address. Test each branch with the published bot; a correct link in your worksheet is no help if the live conversation selects a different event.

Do not have the bot list guessed times such as “Tomorrow at 2 pm is available”. For the link route, say, “The booking page shows available times.” Calendly's Scheduling FAQ explains that available hours, event settings and connected-calendar conflicts control the offered slots. Let that scheduling page resolve availability instead of duplicating its rules in a free-text answer.

Calendly detects time zones automatically and allows adjustment. Ask test visitors to check the zone displayed on the booking page rather than assuming that device detection is always correct. An illustrative visitor's device is set two hours ahead of their intended zone; they must correct that choice before booking. Use explicit start and end times in the final confirmation check.

If no times appear, offer a route back to staff: “No suitable time? Use the enquiry form and tell us when you can talk.” This is a suggested customer message, not a promise that the form creates a booking. Keep the event title in the message so the office knows which discussion the visitor was trying to arrange.

A cleaning company's illustrative customer asks for an evening call, but the owner only offers morning discussions. The bot should not invent an evening slot to be helpful. Its fallback asks the customer to request an alternative. That preserves the owner's working hours and makes the gap between customer preference and bookable time visible.

How do you install the Calendly integration in Botpress?

Install the Calendly integration in Botpress once the plain-link route works, and connect it with a Calendly personal access token. In Studio, open the integrations menu (the puzzle icon in the left-hand menu) or Explore Hub, find Calendly, which the Botpress team maintains, and install it. The setup needs a Calendly personal access token: in Calendly, open Integrations & apps, search for Webhooks, select API and webhooks, then Generate New Token under Your personal access tokens. Name it, for example “Botpress Chatbot”, select Create token and enter the verification code Calendly sends, usually to the account email.

The token is shown only once, so copy it straight into the integration's configuration in Botpress and nowhere else: not a customer message, a knowledge file or a shared document. It is a credential; treat it like a password. Once configured, the integration registers a Calendly webhook subscription for that user, which is how bookings reach the bot. Calendly's developer release note dated 3 November 2026 says webhooks are now available on all plans, including Free, which should let the triggers work on a Free Calendly account; confirm they fire in a test booking before relying on them.

This is where the integration earns its setup time. Each link it generates carries the chat's conversation ID in a tracking parameter, and when the invitee submits Calendly's form, the Event Scheduled trigger arrives with that conversation ID plus the event name, start and end times, location type, organiser, and the invitee's name and email address. In an illustrative test, two visitors both ask about finishes but only one books. Each received a different one-time link, so only the chat that booked is marked, and nobody has to guess.

A booking that does not come through a generated link carries no conversation ID. If a visitor uses your plain event link or the booking page on your own website, the trigger still fires, but the integration cannot tie it to a chat and only logs a warning. Decide in advance what the flow does with an unmatched booking, for example add it to the daily check rather than message anyone, and keep the invitee details it receives to what the follow-up actually needs.

Also test a cancellation and a reschedule before using feedback operationally. The integration's definition lists no separate reschedule trigger, so run a reschedule from the confirmation email in testing and record which triggers fire. A rescheduled discussion should not remain counted as two future calls in your tracking sheet, and a cancelled booking should not trigger a “see you tomorrow” message. Keep evidence from the actual booking rather than relying on chat wording.

Price the two services and check the current API boundary

Calendly's pricing page lists Free with one event type and one calendar connection. Standard is shown at $10 per seat per month on yearly billing, with unlimited event types, multiple calendars, and automations and reminders, which Free does not list. One host can therefore test one standard discussion on Free, but separate events for fitted and standard work, several diaries or reminder emails to cut no-shows all point to Standard.

Botpress has its own conversation billing. Its pricing page lists 100 included conversations for Free without a renewal period beside that figure. Plus is listed at $150 a month billed annually with 250 monthly conversations and $25 of AI usage. A link flow still uses bot conversations; it is not free merely because Calendly completes the final booking outside chat.

An illustrative paid-plan comparison for one host combines Standard's $10 monthly equivalent on yearly billing with Botpress Plus's $150 monthly equivalent on yearly billing: $160 before any extra usage or other services. The annualised arithmetic is $1,920. This is not a recommendation to buy both tiers for a pilot, and it must not be presented as a cancellable $160 monthly package.

Calendly's developer release note dated 3 November 2026 says the Scheduling API is now available on all plans, including Free: its booking endpoint, POST /invitees, no longer requires a paid plan, though the scheduled_events:write permission is still needed. Do not repeat older advice that direct booking always needs a paid plan, and do not read the change as unlimited either. API availability also does not mean the Botpress integration exposes those calls as cards; it does not.

Calendly's rate-limit page sets the real boundary for a non-developer. At the time of writing it lists 50 API requests per user per minute on Free and 500 on paid plans, and for Create Event Invitee, the direct-booking call, just five requests per user per day on Free or trial accounts, against 10 a minute, 50 an hour and 100 a day on paid plans below Enterprise. A bot that booked directly on a Free account would stop after five booking requests in a day, while the link routes above are unaffected because the visitor books on Calendly's own page.

Availability is in the same position. Calendly's API has a List Event Type Available Times endpoint that returns open times for a window of up to 31 days, so a developer could build a “Thursday at 2 pm or 3 pm?” step in chat. The Botpress integration does not include it, which makes it custom code with its own testing and maintenance, and the clearest point at which an owner should hire help rather than keep building.

How do you test a booking bot for completed, abandoned and failed bookings?

Test a booking bot with an illustrative ten-journey acceptance set that scores completed, abandoned and failed bookings as different outcomes. The set is four normal bookings, two visitors who open the link but leave, one unavailable-time case, one wrong-service request, one reschedule and one cancellation. Define expected outcomes in advance. Only the four completed bookings should initially be described as booked; the abandoned visits should remain link handoffs without confirmed appointments. With the integration in place, the four bookings should produce four Event Scheduled triggers carrying four different conversation IDs, and the two abandoned visits should produce none.

For the four normal journeys, check the event in Calendly and the host calendar, then read the customer confirmation. Match host, event type, date, duration and time zone. If your chat receives feedback, inspect that too. Calendly's Scheduling FAQ documents booking notifications and cancellation or reschedule links; verify the specific event's behaviour rather than assuming every reminder option is configured.

For abandonment, close the booking page before submitting it and return to chat. The bot should not announce success. A useful response is, “If you have not received a Calendly confirmation, please reopen the booking link or contact the team.” If you later add reliable event feedback, adapt the wording to the known status, but retain a clear route for uncertainty.

For a simulated connection problem, disconnect only the test integration or use a test bot with missing credentials, keeping the live service untouched. The link route should still be available if that is your chosen fallback. Do not expose the raw token or stack trace to customers. Give them a short practical message while keeping technical evidence for the maintainer.

Add one test the plain link never needed. Each generated link is created for a single booking, so after a test booking, open the same link again in a private window and note what a second person would see. Then check that no branch of the bot re-sends an old link from an earlier message or variable: every visitor who reaches the booking step should receive a freshly generated one.

If the chat itself fails to reply, use the silent Botpress bot checks. If it replies with the right link but the booking page has no times, investigate Calendly's availability settings. This separation prevents a scheduling problem from turning into unnecessary changes to an otherwise working conversation.

If you log your test journeys in a spreadsheet, The Complete Excel Course with AI Integration on Coding Liquids covers the sheet side.

Who records attendance once the bot has booked the call?

Attendance is recorded separately from booking, and a person has to mark it in Calendly. For example, an illustrative finish discussion is correctly booked for 20 minutes, but the visitor does not attend. The booking flow still completed its job; attendance is a later operational outcome. The integration's no-show triggers fire when an invitee is marked, or unmarked, as a no-show in Calendly, so someone still has to mark it; nothing detects attendance automatically. Decide who records the result and test any follow-up, such as a rebooking message, against that recorded status before sending it.

Use a weekly manual reconciliation during the pilot: count confirmed discussions in Calendly, compare them with any booking labels created by your bot and inspect mismatches individually. A missing label may be an integration problem; an extra label may represent a cancelled meeting or an incorrectly matched enquiry. Fix the status logic before using those counts to judge whether the bot generates useful appointments.

A maintenance sheet should name the event owner, approved link, qualifying questions, fallback message and source of booking confirmation. Include one completed test, one abandoned handoff and one cancellation. The owner should be able to explain which system is authoritative for each result. A chat transcript saying “booked” is not enough when the schedule contains no appointment.

Ask a colleague to replace the test event link with another approved test link and trace the changed flow. That checks whether the address is maintained in one understandable place or duplicated across several messages and knowledge files. If five copies must change, consolidate the design before expanding to several services, because stale links become hard to notice.

Give direct booking a clear hiring threshold. Get help when the bot must fetch slots, book without redirecting, prevent duplicate requests, coordinate multiple hosts or write bookings into another system. Request demonstrations for a busy slot, an expired credential and a retry after an uncertain result. The Botpress help-scoping tutorial explains how to make that work reviewable.

For a proposed owner trial, allow 45 minutes to configure and test the event, 45 for the conversation and another hour for the ten journeys. Those are planning budgets, not guaranteed setup times. Finish with the simplest route that passes the evidence checks. A reliable qualifying conversation plus a working booking page can already solve the call-arranging problem without pretending to be a complete scheduling application.

Further reads

Sources: Botpress Calendly integration page and the integration's source code in Botpress's public GitHub repository; Botpress Studio Capture Information, Autonomous Node and Integrations documentation; Botpress pricing page; Calendly pricing page, Scheduling page help article and Scheduling FAQ; Calendly developer release note of 3 November 2026, Rate Limits page and API reference.

Want a second pair of eyes on your setup?

Bring the process you're trying to fix. On a 1:1 call we'll work out which AI tools should handle it, which parts stay manual, and how to roll it out without disrupting the team.

Book a 1:1 call with me