Works with Calendly via Make, Zapier, n8n or the Calendly API

AI Chatbot for Calendly: end the conversation with a booked slot

Nobody books a call from a "Book a call" button on their first visit. They book after someone answers the three questions standing between them and a calendar — do you cover my area, how much is it roughly, how soon could you start. Asyntai answers those on the page, then puts the Calendly link in front of them at the exact moment the objection disappears.

Get Started Free See the setup

See what the chatbot would answer

Enter your website and watch the AI answer questions using your own content — these are the answers that come just before someone picks a time.

Why a Calendly chatbot outbooks a contact form

A booking page is a commitment device pointed at someone who has not decided yet. It asks for a name, an email and thirty minutes of a stranger's diary before anybody has established that the thing is even relevant. Most visitors close it.

The gap is not motivation. It is unanswered questions, and they are almost always the same handful. A chatbot closes that gap in the order a human would: answer, answer, answer, then offer the calendar.

Visitor
Do you work with clients outside the UK?
Chatbot
Yes — we work across the EU and North America, and everything is delivered remotely.
Visitor
And roughly what does a project like ours cost?
Chatbot
Projects of that size usually land between the two figures on our pricing page. The exact number depends on scope.
Visitor
OK, that could work.
Chatbot
Would you like to pick a time to go through scope? Here is the calendar.

That last line is the whole product. It is worth very little on a page that a visitor has already decided to leave, and it is worth a great deal at the end of an exchange where their two real objections were just handled with your own published facts.

The booking link does not need to be smarter. It needs to arrive later in the conversation than a button can.

How to connect the chatbot to Calendly

There are two honest routes, and most sites only ever need the first one.

Route A — no connector

Share your standard booking link

Put your Calendly URL in the AI instructions with one line of guidance about when to offer it, and add it to your knowledge base. That is the entire setup, it works on any plan, and it covers the great majority of cases.

The link is the same for everyone. What is not the same is the timing, and timing is where the bookings come from.

Route B — connector

Create a link for that one visitor

An Asyntai webhook fires, a connector receives it, and the connector calls Calendly to create a scheduling link for that specific person. Needs a paid Asyntai plan and a connector, and gives you a link you can also drop into a follow-up email.

Read the next section before choosing this — there are real constraints on what those links do.

Setting up Route A

Add the Calendly URL to your content. Put it on the page the chatbot reads, or upload it as part of a short document, so the bot can quote it accurately rather than guess at it.
Write one instruction. Something like: offer the booking link once the visitor has shown buying intent or asked about next steps — not in the first reply. The instruction matters more than the link does.
Test it in your own widget. Ask three objection-shaped questions in a row and check the calendar shows up at the end, not at the start.

Setting up Route B

The order matters, because you need the connector's URL before Asyntai has anywhere to send anything.

1. Connector
Custom webhook or Catch Hook gives you a URL
2. Asyntai
Paste the URL, tick your event, set a secret
3. Calendly
Connector creates the scheduling link
4. Deliver
Email or message the link to the visitor
Get a listening URL. In Make use Webhooks → Custom webhook; in Zapier use Webhooks by Zapier → Catch Hook. Pabbly, n8n and your own endpoint work the same way.
Register it in Asyntai. Open Settings → API, paste the URL, tick the event you want — usually escalation.requested — and set a signing secret. Webhooks are on the paid plans.
Send one real chat so the connector learns the field names. In Make, Re-determine data structure reruns this if you change events later.
Add the Calendly step. In Zapier the action is Create One-Off Meeting Link. In Make, the Calendly app includes a module that creates a scheduling link. Then add a step that actually gets the link to the person — an email, an SMS, or a note on their CRM record.
What Asyntai POSTs to the connector
// Headers: Content-Type: application/json // X-Webhook-Event: escalation.requested // X-Webhook-Signature: <HMAC-SHA256 of the body, using your secret> { "event": "escalation.requested", "payload": { "session_id": "s_2c74be10", "message": "Can someone walk me through the onboarding?" } }
Mapping it in a downstream module
Note body: Asked in chat: {{1.payload.message}} Reference: {{1.payload.session_id}} Event type: {{1.event}}

The Asyntai webhook sends only Content-Type, X-Webhook-Event and X-Webhook-Signature. It cannot carry a Calendly token, so Route B always has a connector in it. Anyone promising a one-click Calendly hookup is describing something else.

What a Calendly chatbot can and cannot do with links

This is the part people get wrong, so here is the verified position.

Creating a booking link is possible. Calendly's API v2, at api.calendly.com, includes a Create Single-Use Scheduling Link endpoint: you give it the URI of an event type and it returns a booking URL. It authenticates with a personal access token or OAuth. Calendly's own FAQ states that single-use scheduling links which have not been used to book expire after 90 days. Zapier surfaces the same capability as the Create One-Off Meeting Link action, and Make's Calendly app has a module that creates a scheduling link, so you do not have to write the call yourself.

Booking the slot for the visitor is a different matter. Creating a link is not the same as choosing a time. Calendly documents a one-off meeting link as expiring once it has been booked, and one-off meetings cannot be rescheduled — you cancel and create a new one. The visitor still picks the time on Calendly's own page. Treat "the chatbot books the meeting" as marketing language; what actually happens is that the chatbot removes every reason not to click through.

And for most sites, Route A is the right answer anyway. A single-use link is genuinely useful for private or paid sessions, for a link you are pasting into a personal follow-up, or when you do not want the URL circulating. For a public "talk to sales" flow it adds a moving part without adding a booking.

Two Calendly chatbot flows worth building first

One needs no connector. One does. Start with whichever matches how you actually sell.

Answer the objection, then offer the calendar

Route A, and the one that moves the number. The chatbot handles coverage, price range, lead time and process from your own pages, and offers the booking link only once the visitor signals intent. No webhook, no connector, no API key — the whole thing lives in your AI instructions.

Set the instruction so the bot never leads with the link. A calendar offered before an answer reads as a brush-off, and it converts like one.

Visitor question→Answer from your content→Intent→Booking link

A private link and a briefed salesperson

Route B, for higher-value conversations. When a visitor asks for a person, the connector creates a scheduling link for them, sends it, and — using Calendly's invitee scheduled trigger on the way back — posts a short brief to your sales channel when the slot is taken.

The brief is the good bit. Add an HTTP step that POSTs the visitor's questions to https://asyntai.com/api/v1/chat/ and paste the response into the notification, so whoever runs the call has already read what this person was trying to find out.

escalation.requested→Create scheduling link→Send it→Invitee scheduled→Brief the rep
Asking the chatbot for the brief
// POST https://asyntai.com/api/v1/chat/ // Header: X-API-Key: YOUR_API_KEY { "message": "Summarise what this visitor asked about, in three lines.", "session_id": "s_2c74be10", "website_id": "YOUR_WEBSITE_ID" } // Response { "success": true, "response": "Asked about EU coverage, rough project cost and start dates...", "session_id": "s_2c74be10" }

Reuse the session_id the webhook gave you and the summary is written with that visitor's own thread in view. The endpoint takes the key as an X-API-Key header, an Authorization: Bearer header, or an api_key query parameter for connectors that cannot set headers. Details in the API documentation.

What the Calendly chatbot connection gives you

The link arrives at the right moment

After the objection is answered, not before. That single change in ordering is where the extra bookings come from.

Answers from your own content

Coverage, pricing, lead times and process come from your own pages and uploaded documents — so nothing invented gets promised before a call.

30+ languages

The pre-booking conversation happens in the visitor's language automatically, even when your booking page is English only.

Out of hours, still selling

Evening and weekend visitors get their questions answered and a time on the calendar instead of a form nobody reads until Monday.

Single-use links when it matters

For private sessions or paid consultations, the connector can generate a link for one person rather than exposing a public booking page.

A brief before the call

The chat that led to the booking becomes a short summary, so the meeting does not start with "so, tell me what you need".

What this actually costs

  • Route A. Just an Asyntai plan. The free plan's 100 messages a month is enough to prove that the ordering works before you pay for anything.
  • Route B. Needs Asyntai webhooks or the REST API, which are on the paid plans — Starter, Standard or Pro. See pricing.
  • Calendly. Billed by Calendly, and unchanged by any of this. Check your own tier before relying on a specific action, since connector actions can carry their own plan requirements.
  • The connector. Make, Zapier and Pabbly bill separately and all have free tiers. Self-hosted n8n or your own endpoint adds nothing.

Calendly chatbot questions

Can the chatbot share my Calendly booking link?

Yes, with no connector at all. Put the link in your AI instructions and knowledge base with a note about when to offer it, and the bot hands it over at the right point in the exchange rather than as an opening move.

Can a Calendly link be created for one specific visitor?

Yes. Calendly's API v2 has a Create Single-Use Scheduling Link endpoint that takes an event type URI and returns a booking URL. Zapier exposes it as Create One-Off Meeting Link, and Make's Calendly app has a module that creates a scheduling link. Calendly states that unused single-use links expire after 90 days, and that a one-off meeting link expires once booked.

How does the chatbot trigger the link creation?

Through a connector. Asyntai POSTs signed JSON on four events — message.received, conversation.started, escalation.requested and takeover.started — with no custom auth header, so it cannot carry a Calendly token. Make, Zapier, Pabbly, n8n or your own endpoint holds the Calendly credentials and makes the call.

What happens after the visitor books?

Calendly fires its own invitee scheduled trigger, which the same connector can catch. Log it, post it to a sales channel, or call the Asyntai API to turn the chat into a three-line brief for whoever is taking the meeting.

What does a Calendly chatbot setup cost?

Sharing a link needs only an Asyntai plan, free included. Creating links needs webhooks or the API, which are on Starter, Standard and Pro. Calendly and your connector bill separately.

Other ways to wire the chatbot in

The same four events and the same REST API work through anything that can receive a JSON POST.

Make Zapier n8n Twilio API docs All platforms

Fill the calendar from the conversation

Let the chatbot answer what stands in the way, then hand over the booking link while the visitor is still reading.

Get Started Free