How I Built Thank-You Workflows for Every Calendly Meeting

I forwarded myself one email — a thank-you note that William Jones’s Calendly sent me after I guested on his podcast — with the instruction: do this for all our appointments. My Claude agent read that note, audited every meeting type in my Calendly, and shipped seven personalized thank-you workflows plus five matching landing pages on dennisyu.com. Every meeting I take now says thank you automatically, one hour after it ends.

Start With the Note, Not the Tool

The assignment came from a real experience, which is where every good automation starts. I was a guest on William Jones’s podcast. An hour later his Calendly sent me a short thank-you email. It felt good — and I noticed it felt good. So I forwarded it to myself: build this for every kind of appointment we take, and make each one specific.

The agent’s first move was not opening Calendly. It searched my Gmail, found the forwarded note, read the original thank-you it was based on, and extracted the pattern worth copying: send after the meeting ends, keep it short, invite a reply.

Map Every Meeting Type Before Touching Anything

Diagnosis before prescription. The agent inventoried my Calendly and found 12 event types: nine personal (Quick Audit, Coach Yu podcast, three flavors of private meetings, Power Hour, campaign optimization, VA training, a 15-minute meeting) and three shared team events (VIP Coaching Audit, AI Builder Strategy Call, HRI Knowledge Panel Package).

Only one had any follow-up: Quick Audit. And when the agent opened that email, it found a bug that had been running in production — the body read “Hi [Invitee First Name]” and signed off “Cheers, [Your Name]” as literal text. Real clients had been receiving placeholder brackets. A checklist-follower would have cloned that bug into every new workflow. The agent fixed it at the root with Calendly’s real merge variables.

Ship the Landing Pages First

Calendly’s email editor strips images — the agent tested this by injecting a photo, saving, and reloading (it survived the editor, then the server deleted it). So instead of fighting the platform, it moved the personal touch one click away: five landing pages on dennisyu.com, each opening with my photo, written in my voice, with next steps for that exact kind of meeting. The pages were published through the WordPress REST API — no page builder, no clicking, idempotent by slug.

Automate the Emails Inside Calendly

Rather than build six workflows from scratch, the agent perfected one — the rewritten Quick Audit follow-up — then used Calendly’s Clone function six times. Each clone inherited the proven trigger (send 1 hour after the event ends), got renamed, got its event types re-assigned through the checkbox picker, and got its subject and body rewritten with real merge fields. Typing {{invitee_first_name}} into Calendly’s editor auto-converts to a live variable chip, which the agent verified by saving and reloading every workflow.

Where This Fits the Meetings Checklist

Knowing how to set up Calendly is only as good as the process it lives inside. Every meeting has a before, a during, and an after — that is the exact structure of our Meetings Checklist, and it is the backbone of how we run client onboarding, the welcome and expectations call, and every client call after it.

The thank-you workflow is the automated first move of the AFTER column: coordinate the follow-up, send the notes, assign the tasks. We already automated the audit side of this with Zapier follow-ups for Quick Audit clients — this build extends the same principle to every meeting type. If you run an agency, this is the systemization we teach in the Agency Management Course: meetings are not calendar events, they are a process with deliverables on both sides.

Judge the Five Decisions That Mattered

1. Clone, don’t create. Perfecting one workflow and cloning it six times preserved the tested trigger and email structure. Alternative: building each from scratch — six more chances to misconfigure timing.

2. Test the image limit instead of assuming. The agent injected a photo, saved, reloaded, and proved Calendly strips images server-side. That moved the personal touch to landing pages we control — which is also better for email deliverability. Alternative: shipping an email that silently lost its photo.

3. Fix the placeholder bug at the root. The old email’s literal “[Your Name]” text would have propagated into all six clones. Alternative: automate on top of a broken template.

4. Publish pages by REST API, not page builder. Idempotent by slug — re-running updates instead of duplicating. Alternative: forty minutes of Gutenberg clicking with nothing repeatable.

5. Seven specific emails, not one generic blast. A podcast guest and a VA-training client need different next steps. Grouping 12 event types into 7 contexts kept every email specific without creating 12 near-duplicates to maintain.

Read the Receipts

Separate What the Agent Could and Could Not Do

Could do autonomously: Gmail search and pattern extraction, full Calendly inventory, finding and fixing the placeholder bug, writing all copy in my voice, publishing five pages via REST, building seven workflows through browser automation, and verifying everything persisted.

Could not do: log in (I entered my Calendly and WordPress passwords myself); embed images inside Calendly emails (the platform strips them — solved with landing pages); capture the Calendly admin UI as screenshots (macOS screen-recording permission requires an app restart, so this article uses real renders of the live pages instead); and send a real test booking end to end, since that would put a fake meeting on my calendar.

Count the Ingestion

One Gmail thread pinpointed from a 600-thread search space. Twelve Calendly event types and two existing workflows inspected. Six pages read across dennisyu.com and blitzmetrics.com for voice, links, and entity structure, including the full article guidelines (~3,500 words). Output: ~1,800 words of landing-page copy, ~700 words of email copy across seven workflows, and this meta article.

Score It Against the Guidelines