Calendly no-show follow-up: what one email leaves out
Calendly emails no-shows on Standard and up, once you mark them. Here is the webhook build that adds a text, a second touch and a stop when they rebook.
What you get from this guide
- What Calendly's own no-show automation does, and the plan it needs
- The honest limit: somebody still has to mark the no-show
- The webhook events, scopes, signature header and rate limits, checked against Calendly's developer docs
- A three-touch rebooking sequence with email and SMS copy
- Every stop signal, including the one for a no-show marked by mistake
What Calendly actually ships
Calendly has a no-show feature, and you should use it before building anything. Its help centre article on marking no-shows describes the flow: find the meeting, open its details, choose Mark no-show and confirm. It works on web, mobile and the browser extension, and the button only appears after the meeting's scheduled start time.
The same article says that on the Standard plan or higher you can use automations to send an email to no-shows asking them to book a new time. It also notes a useful side effect: invitees marked as no-shows will not receive your other follow-up emails unless the workflow is set to target no-shows specifically. So the thank-you email does not go to somebody who never arrived.
Start here
Everything in this guide was checked against Calendly's help centre and developer documentation in November 2026. Plans and features change, so confirm what your own account shows before you build.
Where one email falls short
There are four specific gaps, and you should only build for the ones that cost you money.
| Need | Native automation | Built sequence |
|---|---|---|
| One rebooking email | Yes, on Standard and up | Yes |
| A second and third touch | Not described in the help article | As many as you design, with stops |
| A text message | The article describes an email | Yes, from your own registered number |
| Stop when they rebook or reply | Not documented | Yes, driven by invitee.created and inbound replies |
| Outcome written to a CRM | No | Yes |
| Detecting the no-show | Manual click | Still a decision somebody or something has to make |
Read the last row twice. No automation platform removes it. A webhook fires when an invitee is marked as a no-show, not when they fail to join a call. If nobody marks it, nothing happens, in Calendly or in your workflow. The cheapest fix is a habit: the person who ran the meeting marks it within the hour. The more involved fix is to have your own system mark it through the API, which only makes sense if you already hold a reliable attendance signal somewhere else.
A worked example, labelled as illustrative because the numbers are made up for the arithmetic: if you hold 40 consultations a month and 6 do not show, and a rebooked consultation is worth 150 to you on average, then rebooking 2 more of those 6 is 300 a month. Put your own numbers in. If the answer is small, stay native.
What the API gives you
Calendly's webhook subscription reference lists the events you can subscribe to. Four matter here.
| Event | Fires when | Used for |
|---|---|---|
| invitee_no_show.created | An invitee is marked as a no-show | Starts the sequence |
| invitee_no_show.deleted | A no-show mark is removed | Cancels a sequence started by mistake |
| invitee.created | Somebody books | Stops the sequence when the same person rebooks |
| invitee.canceled | A booking is cancelled | Keeps your records honest, and can start a separate flow |
All four accept organization, user or group scope and require the scheduled_events:read auth scope, with webhooks:write to create the subscription. The reference also states that, other than routing form, meeting recap and contact events, all events are available on all Calendly plans, including Free. Subscriptions are created with a POST to https://api.calendly.com/webhook_subscriptions.
Three operational details decide whether the build is reliable.
- Signatures. Calendly sends a
Calendly-Webhook-Signatureheader in the formt=timestamp,v1=signature. The signature guide shows how to compare it against your signing key and reject old timestamps to block replays. - Retries. The webhook errors page says a failing endpoint is retried with exponential back-off for 24 hours, after which the webhook is disabled and has to be recreated. The documented timeouts are 10 seconds to connect and 15 seconds to read, so acknowledge fast and process afterwards.
- Rate limits. The rate limits page gives 500 requests per user per minute on paid plans and 50 on Free, with a 429 response and
X-RateLimit-RemainingandX-RateLimit-Resetheaders. A no-show sequence comes nowhere near either figure.
There is also a Create Invitee No Show endpoint, POST /invitee_no_shows, which needs the scheduled_events:write scope. That is how an external system marks a no-show without anyone opening Calendly.
The three-touch rebooking sequence
Three touches is the ceiling for a missed meeting. The person already agreed to meet you once, so the tone is helpful rather than chasing, and it ends cleanly.
| Touch | Timing | Channel | Job of the message |
|---|---|---|---|
| 1 | Within an hour of the mark | Email, or Calendly's own | Assume good faith, give the rebooking link |
| 2 | Next working day | SMS if you have consent, else email | Short nudge with one or two specific slots |
| 3 | Day 5 | Close out, leave the link, stop |
If you keep Calendly's native email on, treat it as touch one and start your workflow at touch two. Running both from the first hour sends two near-identical emails within minutes of each other.
The build
The steps below are written for n8n with a Webhook node and the HTTP Request node, and they map directly onto Make or Zapier.
Turn on the native email and set the marking habit
Apply the no-show automation to the relevant event types if your plan includes it. Then name the person who marks no-shows and the time they do it. The whole build depends on that click.
Create the webhook subscription
Create a personal access token, find your organization URI, and POST the subscription with all four events and a signing key of your own.
Create the subscription
POST https://api.calendly.com/webhook_subscriptions
Authorization: Bearer <personal access token>
Content-Type: application/json
{
"url": "https://YOUR-N8N/webhook/calendly",
"events": [
"invitee_no_show.created",
"invitee_no_show.deleted",
"invitee.created",
"invitee.canceled"
],
"organization": "https://api.calendly.com/organizations/<ORG_UUID>",
"scope": "organization",
"signing_key": "<a long random secret>"
}Verify, acknowledge, then fetch
Verify the signature header, return a 2xx straight away, and only then do the work. The no-show payload points at the invitee, so call the invitee URI to read the name, email, the event it belonged to and the answers to any booking questions, which is where a phone number lives if you asked for one.
Write the rebooking record
One row per no-show in a sheet, Airtable or Postgres: invitee URI, email, phone, event type, missed start time, status = open, step = 0 and next_touch. Use the invitee URI as the unique key so a retried webhook cannot create a second sequence.
Wire every stop signal
On invitee.created, look for an open record with the same email and stop it. On invitee_no_show.deleted, stop the record for that invitee. Add inbound email and SMS replies and a manual stop. Build these before the send step, not after.
Sweep hourly and send
A Schedule trigger reads open records with a next_touch in the past, re-reads the status, applies quiet hours in the invitee's timezone, sends the touch, then advances step. Do not chain multi-day wait nodes; a restart strands them.
Close out and write back
After touch three, set status = closed_no_response. Push the result to your CRM or a simple report: marked, rebooked, closed. That report is how you find out whether this was worth building.
Message copy
Touch 1 - email, within the hour
Subject: Missed you today - want to pick another time?
Hi {first_name},
We had {event_name} booked for {start_time} and I
did not see you on the call. No problem at all, these
things happen.
Here is the link to pick a new time that suits:
{rebooking_link}
{business}Touch 2 - SMS, next working day
Hi {first_name}, it is {business}. We missed you for
{event_name} yesterday. I have {slot_1} or {slot_2}
free, or pick any time here: {rebooking_link}
Reply STOP to opt out.Sign with the business name, not an individual, and never imply the message was typed by hand if it was not. The broader two-way pattern, including confirmations before the meeting, is in the appointment reminders guide.
Texting rules
Email follow-up to somebody who booked with you is straightforward. Texting is not. In the US, automated messages from a 10-digit number need A2P 10DLC registration, brand first and then campaign, before you send. The A2P 10DLC guide covers the route and the fees. You also need consent that matches what you send: add a line to the booking form saying you may text about this appointment, and honour STOP across every workflow, not only this one.
Testing and measuring it
Test with real bookings on a private event type before any customer sees a message. A webhook build that has only been tested with sample payloads will fail on the first real one.
- Book a test meeting with your own second email address, wait for the start time to pass, and mark it as a no-show. Confirm one record is created and touch one arrives once.
- Remove the no-show mark. Confirm the record is stopped by the deleted event and nothing further sends.
- Mark a second test booking, then rebook with the same email before touch two is due. Confirm the new booking stops the record.
- Reply to touch one by email and, if you text, reply STOP to touch two. Confirm both stop the record and the opt-out is stored.
- Take your endpoint offline for ten minutes, mark a no-show, and bring it back. Confirm Calendly's retry delivers the event and you do not get a duplicate record.
- Mark a no-show outside business hours and confirm the text waits for the morning.
Then measure three numbers for a month: no-shows marked, no-shows rebooked within 14 days, and replies that needed a person. The middle number divided by the first is your rebooking rate. Compare it with the month before you built anything, when the only follow-up was the native email or nothing at all. If the rate has not moved, the problem is upstream: reminders before the meeting, a booking form that attracts the wrong people, or meetings booked too far ahead.
Keep a short weekly check as well. List your webhook subscriptions through the API and confirm the one you created is still active. Calendly disables a subscription that fails for 24 hours, and a disabled subscription is silent. It simply stops sending, and the first you hear of it is a month of no-shows with no follow-up.
Finally, decide who owns the replies. A rebooking message invites answers such as a request for a different day, a question about price, or an apology with a reason. Those go to a named person, during working hours, with the original booking in front of them. An automation that sends three messages and leaves the replies unread is worse than no automation.
Where these builds go wrong
- Nobody marks the no-show, so the webhook never fires and the build is blamed.
- Running Calendly's native email and a custom first touch together, so two emails land in ten minutes.
- Ignoring invitee_no_show.deleted, so a person marked by mistake still gets chased.
- Not subscribing to invitee.created, so somebody who already rebooked gets touch two.
- Doing slow work before acknowledging the webhook and tripping the documented timeouts.
- Letting the endpoint fail for a day, after which Calendly disables the subscription.
- Texting a number collected without consent wording, or from an unregistered US number.
- A guilt-trip tone. The person can simply book with someone else.
If booked consultations are how work arrives, this pairs naturally with missed call text-back. Sector context is on the law firms and accounting firms pages, and what an automation build costs covers the money side.
Sources checked
Every technical claim above was checked against these Calendly pages in November 2026.
FAQ
- Does Calendly automatically follow up with no-shows?
- Partly. Calendly's help centre says that on the Standard plan or higher you can use automations to send an email to no-shows asking them to book a new time. It is triggered when you mark the invitee as a no-show, which is a manual click. So the follow-up is automatic, the detection is not, and the documented message is an email.
- Can Calendly detect a no-show by itself?
- Not according to its documentation. The help article describes a person opening the meeting details and choosing Mark no-show, and notes the button only appears after the scheduled start time. The API has a matching endpoint that marks an invitee as a no-show, so you can do it from your own system, but something still has to decide that the person did not turn up.
- Is there a Calendly webhook for no-shows?
- Yes. The webhook subscription reference lists invitee_no_show.created and invitee_no_show.deleted alongside invitee.created and invitee.canceled. All four can be subscribed at organization, user or group scope and need the scheduled_events:read auth scope. The deleted event fires when a no-show mark is removed, which is your signal to cancel a sequence that should never have started.
- Do I need a paid Calendly plan for webhooks?
- As of November 2026 the API reference states that, apart from routing form, meeting recap and contact events, all other webhook events are available on all Calendly plans, including Free. That includes the invitee and no-show events this build uses. The native no-show email is different: the help centre documents it as Standard plan or higher. Rate limits also differ by plan, at 50 requests per user per minute on Free and 500 on paid plans.
- Can I send the no-show follow-up by text?
- Calendly's help article describes the no-show automation as an email. To text, you send from your own messaging provider, using a phone number you collected at booking with clear consent wording. In the US that means A2P 10DLC registration for a 10-digit number before you send anything automated.
- How do I stop the sequence when the person rebooks?
- Subscribe to invitee.created as well. When a new booking arrives, match the invitee email against open rebooking records and set the status to stopped. Then re-check that status immediately before every send, because a booking made two minutes before a queued message otherwise loses the race.
- Is this worth building if I only get a few no-shows?
- Often not. If no-shows are rare and the meeting is low value, turn on the native email, make marking no-shows a habit and stop there. The build earns its place when a missed meeting is a sales call or a paid consultation, when you want a text as well as an email, or when you need the outcome in a CRM rather than in somebody's memory.
- What does it cost to have this built?
- This is a small workflow: one webhook, one state table, three messages and a handful of stop signals. The variable is what it has to write back to, and whether texting needs registering first. We quote a fixed price in writing per scoped workflow after a free consult, and the automation build cost page explains what moves the number.
Done for you
Want missed consultations rebooked without anyone chasing them?
We build the rebooking sequence around the Calendly account you already have: the webhook, the state table, every stop signal, registered texting and the write-back to your CRM. The audit that scopes it is free.
The consult is free, and you keep whatever we build.
Keep building
The rest of the cluster
AI Appointment Reminders That Cut No-Shows
Two-way confirm and reschedule, waitlist backfill, cadence, and SMS compliance basics.
Read the guideSquare Appointments No-Show Follow-Up Build
The NO_SHOW booking status, the booking.updated webhook, the Plus or Premium gate, and a two-touch rebooking sequence.
Read the guideA2P 10DLC Guide for SMS Automation Builds
Brand then campaign, the sole proprietor route and its caps, published fees, and the real rejection reasons.
Read the guideFree AI Automation Audit Template
Score every recurring task and rank the top three worth automating before you build anything.
