On this page
Connecting Calendly to VGraple CRM syncs every booking, cancellation and reschedule made on your existing Calendly account into the Appointments calendar automatically, matched to the right WhatsApp contact by phone number. This walkthrough covers connecting your account, understanding real-time versus polling sync, and what stays true to your existing Calendly setup afterward.
Calendly: first 5 of 7 steps
- 1Open Integrations settings
- 2Click Connect Calendly
- 3Confirm the connection
- 4Check which sync mode you were assigned
- 5Match event type names to your Service
Before you start
- You need an existing Calendly account; VGraple CRM connects to Calendly, it does not create one for you.
- You need the permission that grants access to organisation settings, included in Owner and Admin roles by default. A regular agent role can view synced appointments but cannot connect or disconnect Calendly.
- Real-time webhook sync requires a Calendly plan that supports webhooks (Calendly's Standard tier or above); a free Calendly account still syncs, but on a polling schedule instead.
- Match your Calendly event type names to your Service Catalog entries under Settings > Services beforehand if you want full variable support (service name, price, duration) in any flow triggered by a Calendly booking.
Steps
- Open Integrations settings. From the sidebar, go to Settings, then Integrations, and find the Calendly card.
Click Connect Calendly. You are redirected to Calendly to authorise the connection; sign in if needed and approve the requested access.
Confirm the connection. After authorising, you land back on the Integrations page with the Calendly card now showing Connected, your Calendly account name and email, and a sync mode badge (Real-time or Polling).
Check which sync mode you were assigned. Real-time (webhook-based) reflects a new booking within moments; Polling checks roughly every 5 minutes. If you see Polling and want real-time, upgrade your Calendly account to a plan with webhook support, then reconnect from this same screen.
Match event type names to your Service Catalog, if relevant. Under Settings > Services, add or rename entries so their names match your Calendly event types exactly, giving any flow triggered by an "Appointment booked" trigger access to the correct service name, price and duration as variables.
Test with a real booking. Book a slot through your own public Calendly link and confirm it appears on the Appointments calendar within the expected sync window, matched to the right contact if the booker provided a phone number Calendly captured.
Disconnect if you ever need to. From the same Calendly card, click Disconnect. New bookings stop syncing immediately; every appointment already created from a past sync remains untouched.
What you will see
The Calendly card shows a green Connected badge, your Calendly account's name and email, the date you connected, and a sync mode badge, a lightning icon for Real-time or a clock icon for Polling. Every Calendly booking that matches becomes an ordinary entry on the Appointments calendar, indistinguishable from one captured directly through a chatbot except for its source, and a cancellation or reschedule made in Calendly updates that same appointment record rather than creating a duplicate.
Settings and options
| Setting or field | What it does | Default |
|---|---|---|
| Connect Calendly | Starts the OAuth authorisation flow with your Calendly account | Not connected |
| Sync mode | Real-time (webhook) or Polling, assigned automatically based on your Calendly plan | Determined by your Calendly plan at connection time |
| Disconnect | Stops syncing new bookings; keeps already-synced appointment history | Available to Owner and Admin roles |
| Service Catalog matching | Aligns Calendly event type names with internal service records for flow variables | Manual, done under Settings > Services |
Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| A Calendly booking never appeared | The connection expired or was revoked from the Calendly side, or the invitee's event type falls outside your Calendly account's scope | Reconnect from Settings > Integrations; check the booking was made on the same Calendly account you connected |
| Booking appears but is not matched to a contact | The invitee did not provide a phone number when booking on Calendly | Expected behaviour; the appointment still exists and can be linked to a contact manually from its detail view |
| Sync feels slow, taking several minutes | Your Calendly account is on Polling mode, which checks roughly every 5 minutes rather than instantly | Upgrade your Calendly plan to enable webhooks, then reconnect for Real-time mode |
| A cancelled Calendly booking still shows as Scheduled | A sync delay, more likely under Polling mode | Wait for the next poll cycle, or reconnect to force a fresh sync if it persists |
| A flow tied to "Appointment booked" did not fire for a Calendly booking | The flow's trigger type was not set to appointment_booked, or no flow with that trigger exists yet | Build or check the flow in Flow Builder; see managing appointments for how reminder and booking triggers work |
| Reconnecting created a duplicate of an already-synced appointment | This should not happen under normal use since sync matches on the underlying Calendly event | Check the two entries carefully; if genuinely duplicated, keep the more recent one and delete the other manually |
Does Calendly stay my calendar of record?
Yes, entirely. Calendly's own connections to Google Calendar or Outlook, if you already had them set up, keep working underneath it exactly as before you connected VGraple CRM. VGraple CRM listens for Calendly's webhook events (invitee created, invitee canceled) or, on Polling mode, checks periodically for the same changes, and mirrors each one as an appointment record. Nothing about connecting Calendly changes how availability, buffer times or your existing calendar integrations behave on the Calendly side.
Example
A clinic keeps its Calendly page as the public booking link shared on its website and in WhatsApp replies. A patient who books through that link shows up on the VGraple CRM Appointments calendar within moments, matched to their WhatsApp contact if Calendly captured their phone number, so the front desk sees it alongside bookings taken directly over chat without checking two separate systems.
Who typically needs this integration, and who does not?
Calendly connection is worth setting up specifically for a business that already runs a public booking page outside WhatsApp and wants that existing workflow to keep working while also landing on the same calendar as conversational bookings. A clinic or coaching institute that shares its Calendly link on its website, in email signatures, or in paid ad landing pages is the clearest fit, since disconnecting that habit and forcing every booking through a WhatsApp chatbot instead would lose the traffic that never opens WhatsApp at all. A business with no existing Calendly presence, starting fresh, is usually better served booking directly inside WhatsApp through a chatbot flow or the AI assistant's appointment action, since that skips an extra account and an extra sync step entirely.
Example
A coaching institute runs Facebook Lead Ads that route to a "Book a Free Counselling Call" Calendly link, a pattern that predates its VGraple CRM setup. Connecting Calendly here means every one of those bookings lands on the same Appointments calendar as a walk-in customer who books by chatting directly on WhatsApp, without the institute having to redirect its existing ad funnel.
Once Calendly is connected, build reminder flows that fire off the same appointment records regardless of whether the booking came through Calendly or a WhatsApp chatbot, since both land on the same calendar.