Go from Calendly to Google Workspace
The job: Basic appointment booking (Booking page, Availability, Timezone handling, Calendar events, Reminders). Pick where you are today and where you want to land; the move below follows your pick.
Every way to do this job · pick one
Switch app
Already in a plan you pay for
Open source
Build it with an agent
Agent skill
The money
$12/mo today , then $0/mo
Calendly Standard
Modeled from public list prices, with your time at $50 an hour. Show the math
Does it do the job? 2 of 2 covered
- Covered: Booking links
- Covered: Calendar sync
Checked against Calendly's own features.
The work
- Setup
- About 30 min
- Upkeep
- None
- Watch out
- Check first: First compare free Calendly and hosted alternatives
Make the move in four steps
Export from Calendly
Contacts: Contacts page: select contacts and export as a downloadable CSV, delivered via an emailed link.
Export stepsSet up Google Workspace
Workspace includes appointment booking pages on eligible plans.
DetailsSwitch links and integrations
Point links, embeds and integrations at Google Workspace, then send a test through every one.
Cancel Calendly
Turn off renewal before your renewal date, once the new setup works. Access runs until: The end of the current subscription term; then the account continues as a Free Account.
How to cancel Calendly
The whole recipe: 10 ways out, best first
What you use
- Booking page
- Availability
- Timezone handling
- Calendar events
- Reminders
Not covered
- Complex round-robin
- Multi-resource scheduling
- Enterprise routing
- Guaranteed external calendar uptime
Check before switching
- First compare free Calendly and hosted alternatives
- OAuth and daylight-saving tests pass
- Calendar conflicts handled
Agents: get_recipe("booking-page") on the Stackcut MCP server.
10 ways out, best first
How we got this
| You pay now: Calendly Standard | $12/user/mo × 1 user | $12/mo |
|---|---|---|
| New cost: Google Workspace | already in a plan you pay for | $0/mo |
| Difference each month | $12 − $0 | +$12/mo |
| Over 12 months | +$12 × 12 | +$144 |
| Setup, once | 0.5 h × $50/h | −$25 |
| Year one | +$144 − $25 | +$119 |
- Not counting your time (0.5 h in year one): saves $144 in year one.
Year one = 12 × (what you pay now − the new cost − upkeep) − setup, with your time at $50/hour. Prices are public list prices; hours are Stackcut’s planning estimates. Price it for your team
How we got this
| You pay now: Calendly Standard | $12/user/mo × 1 user | $12/mo |
|---|---|---|
| New cost: zcal (free tier) | free plan | $0/mo |
| Difference each month | $12 − $0 | +$12/mo |
| Over 12 months | +$12 × 12 | +$144 |
| Setup, once | 1 h × $50/h | −$50 |
| Year one | +$144 − $50 | +$94 |
- Not counting your time (1 h in year one): saves $144 in year one.
Year one = 12 × (what you pay now − the new cost − upkeep) − setup, with your time at $50/hour. Prices are public list prices; hours are Stackcut’s planning estimates. Price it for your team
How we got this
| You pay now: Calendly Standard | $12/user/mo × 1 user | $12/mo |
|---|---|---|
| New cost: TidyCal (free tier) | free plan | $0/mo |
| Difference each month | $12 − $0 | +$12/mo |
| Over 12 months | +$12 × 12 | +$144 |
| Setup, once | 1 h × $50/h | −$50 |
| Year one | +$144 − $50 | +$94 |
- Not counting your time (1 h in year one): saves $144 in year one.
Year one = 12 × (what you pay now − the new cost − upkeep) − setup, with your time at $50/hour. Prices are public list prices; hours are Stackcut’s planning estimates. Price it for your team
How we got this
| You pay now: Calendly Standard | $10/user/mo × 1 user | $10/mo |
|---|---|---|
| New cost: Cal.com Free | free plan | $0/mo |
| Difference each month | $10 − $0 | +$10/mo |
| Over 12 months | +$10 × 12 | +$120 |
| Setup, once | 1 h × $50/h | −$50 |
| Year one | +$120 − $50 | +$70 |
- Not counting your time (1 h in year one): saves $120 in year one.
Year one = 12 × (what you pay now − the new cost − upkeep) − setup, with your time at $50/hour. Prices are public list prices; hours are Stackcut’s planning estimates. Price it for your team
How we got this
| You pay now: Calendly Standard, 1 seat (monthly billing) | $12/user/mo × 1 user | $12/mo |
|---|---|---|
| New cost: Agent skill: propose meeting times by email | runs in the agent you already pay for | $0/mo |
| Your upkeep time | 0.5 h/user/mo × 1 user × $50/h | $25/mo |
| Difference each month | $12 − $0 − $25 | −$13/mo |
| Over 12 months | −$13 × 12 | −$156 |
| Setup, once | 1 h × $50/h | −$50 |
| Year one | −$156 − $50 | −$206 |
- Not counting your time (7 h in year one): saves $144 in year one.
Year one = 12 × (what you pay now − the new cost − upkeep) − setup, with your time at $50/hour. Prices are public list prices; hours are Stackcut’s planning estimates. Price it for your team
- Tested by Stackcut: all 14 test emails passed a strict check in round 1, including requests across the UK and US clock changes, a reschedule and a group call; an independent round (a fresh agent ran every case, a separate agent graded it) passed 14 of 14. our test
- A script does the time-zone and daylight-saving math, not the model: 0 errors in 800 random requests across 18 time zones. our test
- No new subscription if you already pay for an agent that runs skills: a skill is a folder of files the agent loads. agentskills.io
- Drafts only: nothing is sent or booked without a person, and adding the .ics file invites nobody. our test
- No booking page: guests can't pick their own time, and offered times aren't held until someone confirms. our test
- A person reviews every reply and adds every event. At $50/h that costs more than the $12 seat unless you'd answer these emails anyway. our test
- Cal.com's individual plan is free forever, with unlimited event types and calendars and email and SMS notifications, so it may already cover you. cal.com
- Calendly's own Free plan keeps a booking page (one event type, one calendar connection) but drops reminders. calendly.com
Step-by-step: set up, move your data, check, roll back · about 1 h (estimate)
Keep arranging meetings by email. Your agent finds three open times from your rules and calendar, drafts the reply, and writes an .ics event once a time is agreed. You send the reply and add the event.
Budget about an hour to put in your own availability rules and calendar export. Building and testing the skill took Stackcut about 37 minutes of agent time; each test round took about 7 minutes.
Before you start
- Export your scheduled events before you downgrade: filter the Meetings page by date and export a CSV. help.calendly.com
- Write down your event types, working hours, buffers, notice and days off. They go into references/availability.json.
- Decide how the agent reads busy times: a read-only calendar connection, or an .ics export you refresh.
Set up
- Use the Agent Skills layout: SKILL.md plus references/ and scripts/. The script needs only Python 3.9 or later, with no packages or network. agentskills.io
- Put your hours, meeting lengths, buffer, notice, days off, reminders and video link in references/availability.json. Keep the keys. our test
- Connect your calendar read-only, or export .ics. Never give the agent a calendar tool that writes.
- Write 10 to 15 real-looking requests, including one across a clock change and one reschedule, before the first real email. our test
Move your data
- Swap the booking link in your email signature and website for a 'reply to set up a time' line, or keep Calendly Free for the link.
- Existing Calendly bookings stay in your calendar, and the skill reads them as busy time like any other event.
Check it worked
- Have one agent run the test requests and a separate agent grade them with tests/check_slots.py. Fix the skill, not the drafts. our test
- After any change to the script, run tests/verify_extra.py --fuzz to compare it against an independent brute force. our test
- Spot-check real drafts for the first two weeks, especially any that cross a clock change.
Roll back
- A downgrade to Free only takes effect at the end of your billing cycle, and you keep paid features until then, so you can switch back before it ends. calendly.com
Watch out for
- The US and Europe change clocks on different dates (in 2026, 25 Oct in the UK and EU and 1 Nov in the US), so the gap changes by an hour for a week, and Arizona doesn't change at all. Let the script convert every time. our test
- Offered times aren't reserved, so two people can accept the same slot. Re-check every acceptance before confirming, and add the .ics straight away. our test
- An .ics export is a snapshot. Re-export or re-read the calendar before you confirm a time. our test
- The reminder is an alarm in the .ics file, so it reminds whoever adds it. The skill sends no reminder emails to guests. our test
- Calendly payments are generally non-refundable, so downgrade before your renewal date. calendly.com
Reviewed 2026-09-29.
How we got this
| You pay now: Calendly Standard | $12/user/mo × 1 user | $12/mo |
|---|---|---|
| New cost: Google Calendar MCP server | runs in the agent you already pay for | $0/mo |
| Your upkeep time | 0.5 h/user/mo × 1 user × $50/h | $25/mo |
| Difference each month | $12 − $0 − $25 | −$13/mo |
| Over 12 months | −$13 × 12 | −$156 |
| Setup, once | 2 h × $50/h | −$100 |
| Year one | −$156 − $100 | −$256 |
- Not counting your time (8 h in year one): saves $144 in year one.
Year one = 12 × (what you pay now − the new cost − upkeep) − setup, with your time at $50/hour. Prices are public list prices; hours are Stackcut’s planning estimates. Price it for your team
How we got this
| You pay now: Calendly Standard | $12/user/mo × 1 user | $12/mo |
|---|---|---|
| New cost: Google Workspace CLI (gws) and its agent skills | runs in the agent you already pay for | $0/mo |
| Your upkeep time | 0.5 h/user/mo × 1 user × $50/h | $25/mo |
| Difference each month | $12 − $0 − $25 | −$13/mo |
| Over 12 months | −$13 × 12 | −$156 |
| Setup, once | 2 h × $50/h | −$100 |
| Year one | −$156 − $100 | −$256 |
- Not counting your time (8 h in year one): saves $144 in year one.
Year one = 12 × (what you pay now − the new cost − upkeep) − setup, with your time at $50/hour. Prices are public list prices; hours are Stackcut’s planning estimates. Price it for your team
How we got this
| You pay now: Calendly Standard | $10/user/mo × 1 user | $10/mo |
|---|---|---|
| New cost: Replace with AI: custom scheduler | hosting and API costs (modeled) | $15/mo |
| Your upkeep time | 0.5 h/mo × $50/h | $25/mo |
| Difference each month | $10 − $15 − $25 | −$30/mo |
| Over 12 months | −$30 × 12 | −$360 |
| Setup, once | 6 h × $50/h + $100 one-time | −$400 |
| Year one | −$360 − $400 | −$760 |
- Not counting your time (12 h in year one): costs $160 more in year one.
Year one = 12 × (what you pay now − the new cost − upkeep) − setup, with your time at $50/hour. Prices are public list prices; hours are Stackcut’s planning estimates. Price it for your team
How we got this
| You pay now: Calendly Standard | $12/user/mo × 1 user | $12/mo |
|---|---|---|
| New cost: Rallly | a small server (modeled) | $5/mo |
| Your upkeep time | 2 h/mo × $50/h | $100/mo |
| Difference each month | $12 − $5 − $100 | −$93/mo |
| Over 12 months | −$93 × 12 | −$1,116 |
| Setup, once | 4 h × $50/h | −$200 |
| Year one | −$1,116 − $200 | −$1,316 |
- Not counting your time (28 h in year one): saves $84 in year one.
Year one = 12 × (what you pay now − the new cost − upkeep) − setup, with your time at $50/hour. Prices are public list prices; hours are Stackcut’s planning estimates. Price it for your team
How to leave Calendly
Export first
- Contacts: Contacts page: select contacts and export as a downloadable CSV, delivered via an emailed link. (CSV) calendly.com
- Scheduled events / meetings: Filter the Meetings page by status or date range and export; includes invitee name, timezone and contact info, event details, UTM/Salesforce fields, GDPR consent status, and Stripe/PayPal payment data. (CSV) help.calendly.com
- Analytics dashboard history: View aggregated booking analytics in-app; not a file export.. A Calendly community manager said the Analytics page caps history at 365 days; older data must be pulled via the Meetings page export instead. community.calendly.com
What you lose
- More than 1 event type or more than 1 connected calendar
- Workflows (automated reminders and follow-ups)
- Routing forms, lead qualification and round-robin distribution
- CRM/marketing integrations (HubSpot, Salesforce, Mailchimp, Zapier, Marketo, MS Dynamics)
- Notetaker AI recordings/transcripts and automatic meeting recording
- Callie AI email-scheduling assistant
- Stripe/PayPal payment collection on bookings
- Removing Calendly branding and custom confirmation redirects
- Team scheduling analytics and centralized admin/domain controls
- SSO/SAML (Enterprise) and 24/7 chat/phone support
Cancel
- Admin Center → Billing → Change plan → Upgrade/Downgrade → select the Free plan.
- Takes effect
- At the end of your current billing cycle; you keep paid features until then.
- Refunds
- Payments are generally non-refundable, as Calendly's terms say, though support may review special cases.
- After you cancel
- You land on the Free plan: One event type, one calendar connection, one-on-one scheduling only; no automations or reminders.
Tested by Stackcut
Calendly seat → an agent skill that proposes meeting times by email
Question. Can a skill folder (SKILL.md, reference files and a small zoneinfo script) answer meeting requests by email well enough to drop a Calendly Standard seat? It has to offer three open times in the requester's time zone, draft the reply, and write an .ics event with reminders once a time is agreed. Path: Agent skill: propose meeting times by email.
Tested on. Harbor & Pine Studio (a made-up design studio): A fictional one-person studio on Chicago time with a realistic calendar export: repeating events with a skipped week and a moved instance, a cancelled call, all-day busy and free events, times in UTC, London time and a Windows time-zone name, plus a teammate's busy list.
Numbers
- 14 test emails, including clock-change, reschedule, group and day-off cases
- Pass rate by round: 14 of 14 in round 1; independent round (fresh runner, separate grader): 14 of 14
- 0 errors in 800 random requests across 18 time zones
- The checker caught 18 of 18 seeded mistakes
- About 7 minutes of agent time per test round
Verdict
Exact scheduling math and sendable drafts for people who arrange meetings by email, but not a drop-in Calendly replacement. There's no booking page, a person handles every reply, and that time costs more than the $12 seat. An independent round (fresh runner, separate grader) also passed 14 of 14.
Good fit when
- You schedule by email anyway (clients who won't use booking links, requests across time zones)
- You don't want a scheduling service connected to your calendar
- One person's calendar, plus a teammate's busy times for group calls
Not a fit when
- Guests should pick their own time from a public page
- Guests need reminder emails or texts
- You book more than a few meetings a week and want it hands-off
- A free booking-page plan (Calendly Free, Cal.com) already covers what you use
What we found
- The model never did the math. Every time in every draft is a line the script printed. In 800 random requests (18 time zones, including India at +5:30 and Nepal at +5:45, across the US clock change), the script's openings matched an independent brute force exactly: 1,909 slot lines, 0 errors.
- The clock-change traps are real. The UK changed clocks on 25 Oct 2026 and the US on 1 Nov, so London was 5 hours ahead of Chicago for one week and 6 hours otherwise, and Arizona went from 2 to 1 hour behind. A model converting with today's gap gets these wrong. The checker caught all 18 mistakes we seeded, including these.
- Reading real calendar exports is most of the work: repeating events with exceptions, cancelled and free events, all-day busy days and non-standard time-zone names. The script stops with an error on anything it can't read exactly instead of guessing.
- The author's round passed all 14 cases, run and graded by the agent that wrote the skill; the checker, mutation and fuzz results don't depend on that. An independent round afterwards (a fresh agent read the emails and picked dates, zones and attendees itself; a separate agent graded it) also passed 14 of 14.
- It isn't self-serve. There's no booking page, offered times aren't held, and a person sends every reply and adds every event. At $50/h that time costs more than a $12 seat, and Cal.com's free plan and Calendly Free already give a booking page for $0.
How we tested
- Wrote the skill in the agentskills.io format. SKILL.md has the steps, the output block and a Never list. references/ holds the availability rules (a JSON file the script reads), a situations table, time-zone mapping, reply templates and calendar sources. scripts/slots.py (Python standard library and zoneinfo, no network) does every date, time-zone and buffer calculation and writes the .ics file.
- Built a synthetic calendar export with what real exports contain: weekly, fortnightly and monthly repeats with a skipped week and a moved instance, a cancelled call, all-day busy and free events, and times in UTC, London time and a Windows time-zone name. Added a teammate's JSON busy list.
- Wrote 14 realistic emails, a pass/fail rubric and a hand-made answer key before the first run. The hard cases: requests across the 2026 clock changes (UK 25 Oct, US 1 Nov) from London and Arizona, no time zone given, a fully booked week, a 90-minute workshop, a time inside the buffer after a call, a day off, a reschedule, a group call with a second person's busy times, an accepted time that has since been taken, a weekday that doesn't match the date, a request for a booking link and a deposit, and a Saturday-only request.
- The author's round: the runner and the grader were separate passes by the agent that wrote the skill (no Agent tool in that session). The runner read only the skill folder, the emails and the calendar files; the grader read the rubric, the references and the run, and ran the checker.
- The checker (tests/check_slots.py) doesn't use the skill's script. It re-derives every offered time from the hand-written answer key with zoneinfo, checking working hours, the buffer, days off, notice, the requester's hours, every attendee's busy times, the zone label and the abbreviation. It also checks the .ics files byte by byte. Because the runner wasn't fresh, we added two checks that don't depend on who ran the cases: 18 typical agent mistakes seeded into copies of the run (the checker had to catch each one), and 800 random requests to the script compared against an independent brute force.
- After the skill was final, Stackcut ran one independent round: a fresh runner agent (skill folder and case inputs only) and a separate grader agent (rubric, references, checker). Result: 14 of 14.
Compare before you switch
Read the checked comparisons and workload guides for the tools this recipe replaces.
- Calendly vs Cal.com Checked comparison evidence, migration details, public switching accounts.
- Calendly vs Cal.diy Checked comparison evidence, migration details.
- Calendly alternatives in 2026: what to use instead, and what it really costs Compare the wider set of alternatives and their tradeoffs.
More Scheduling recipes
All 139 recipes · Savings leaderboard · Every vendor, with prices and cancel steps