Skip to content

Hourly

Mark no-shows in Calendly for you

An hour after each meeting, invitees are marked as no-shows unless you said they attended, and you get a summary.

Runs
Hourly
Apps
Calendly
AI
Not needed
Access
PAT (read+write)

Send this to your assistant

Create a ClickRuntime automation: an hour after each Calendly meeting ends, mark the invitee as a no-show unless I've replied 'attended' to the summary email, then email me who was marked.

Paste it into your assistant. It tells you what it will send or change before it runs live.

First time? Adding ClickRuntime to your assistant takes about two minutes.

Why use it

Why teams use this automation

Calendly's no-show marking is a manual job. After a day of calls, the host is supposed to open each event and mark the invitees who never joined, so that reporting is accurate and follow-up workflows can fire. In practice, nobody does this at 5 pm after back-to-back meetings, so no-shows go unmarked, show-up rates look better than they really are, and the people who missed a call get no follow-up.

Every hour, ClickRuntime lists the events that ended in the last hour and skips any whose invitees are on an attended list kept in state. It marks the remaining invitees as no-shows in Calendly and emails you a summary of who was marked. The attended list is what protects people who did join from being marked by mistake.

Sales teams and service businesses that track attendance for reporting, billing or follow-up will find it valuable.

What you get out of it

  • Attendance reports reflect reality

    With no-shows marked consistently, your show-up rate is an honest figure. Decisions about reminders, scheduling windows and deposits rest on actual behavior. Clean data in Calendly also keeps any reports or workflows that depend on attendance trustworthy over time.

  • Follow-up can start the same day

    A no-show that is recorded within the hour can trigger an outreach while the missed meeting is still fresh. A quick note offering another time often rescues the lead. Hosts can leave when the day ends, knowing attendance was recorded for them without a final round of clicking.

  • Manual end-of-day cleanup disappears

    Marking no-shows is a chore that is easy to postpone and forget. Doing it automatically each hour frees people from reviewing every call after a long day. Fairness matters most where a missed meeting leads to a fee or a lost priority slot.

  • The attended list prevents mistakes

    Invitees on the attended list are skipped, so someone who did join is not wrongly marked. That keeps the record fair, which matters if no-shows have consequences such as fees.

  • A summary email gives oversight

    Each run reports who was marked, so a person can spot and correct an error quickly. Automation does the bulk of the work while a human keeps the final say. Trust in the automation grows as the summaries prove accurate.

How it works

What happens, step by step

  1. Every hour, ClickRuntime checks your Calendly meetings that ended in the last hour.

  2. It skips anyone you have said attended, and anyone already marked as a no-show.

  3. Everyone else from those meetings is marked as a no-show in Calendly.

  4. You get an email listing who was marked and which meeting they missed.

Before it runs live

  • Connect Calendly

What you get

RunsHourly
Mark no-shows in Calendly for youtoday, 9:00Succeeded
Email · Marked 2 no-show(s)Jordan Park – Product demo Riley Chen – Onboarding call

Build your own

Need it to work differently?

This template is a starting point. Copy the prompt and change it, or describe a different automation from scratch, with your own conditions, more apps or an AI step. Your assistant writes it, tests it and runs it on ClickRuntime.
  • Your own rules

    Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.

  • Any number of apps

    One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.

  • AI where it helps

    Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.

  • On a schedule or on each event

    Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

Changes you can ask for

  • Run it at a different time, more or less often, or only on weekdays
  • Add an AI step, for example to summarize, sort or draft a reply
  • Add another app, for example also send it to Slack
  • Combine it with other Calendly steps into one automation

Under the hood

The code that runs this automation

This is the Python script that runs each time the automation starts. Your AI assistant writes it for you when you send the prompt, and you allow each step in your assistant. To change how the automation works, describe the change to your assistant and it updates the script for you. For every function it can use, see the script reference.
auto_mark_no_shows.pyexample
from datetime import datetime, timedelta, timezone
from clickruntime import on_trigger, credentials, http, state, notify

API = "https://api.calendly.com"

@on_trigger
def run(event):
    h = {"Authorization": f"Bearer {credentials.secret('CALENDLY_TOKEN')}"}
    me = http.get(f"{API}/users/me", headers=h).json()["resource"]["uri"]
    now = datetime.now(timezone.utc)
    events = http.get(f"{API}/scheduled_events", headers=h, params={
        "user": me, "status": "active",
        "min_start_time": (now - timedelta(hours=3)).isoformat(), "max_start_time": now.isoformat(),
    }).json()["collection"]
    attended = set(state.get("attended") or [])
    marked = []
    for ev in events:
        ended = datetime.fromisoformat(ev["end_time"].replace("Z", "+00:00"))
        if not (now - timedelta(hours=2) < ended <= now - timedelta(hours=1)):
            continue
        uuid = ev["uri"].rsplit("/", 1)[-1]
        for inv in http.get(f"{API}/scheduled_events/{uuid}/invitees", headers=h).json()["collection"]:
            if inv["email"] in attended or inv.get("no_show"):
                continue
            http.post(f"{API}/invitee_no_shows", headers=h, json={"invitee": inv["uri"]})
            marked.append(f"{inv['name']} – {ev['name']}")
    if marked:
        notify.email_me(f"Marked {len(marked)} no-show(s)", "\n".join(marked))
    return {"marked": len(marked)}

FAQ

Common questions

How does it know who attended?
Calendly does not report attendance by itself, so the workflow relies on an attended list kept in state, which can be filled from another source such as your meeting tool. Anyone not on the list is treated as having missed the event.
Could it mark someone as a no-show by mistake?
It can if the attended list is incomplete, so keeping that list accurate matters. The hourly summary email shows who was marked, which lets you reverse an error in Calendly. Start by running it alongside your own checks.
Does Calendly need a specific plan for no-show marking?
Marking no-shows is a Calendly feature that depends on your plan and the API permissions of your token. Confirm that your account supports it before relying on the workflow. The token is kept as a secret in the ClickRuntime dashboard.
What permissions does it need?
PAT (read+write). Nothing else in your accounts is used.
Does it need AI?
No. It runs without AI, so it doesn't use your plan's AI allowance.
How many runs does it use?
One run each time it runs (hourly). Checks that find nothing to do and stop right away aren't counted.
Can I change how it works?
Yes. Describe the change to your AI assistant, for example a different schedule, channel or filter. It updates the automation, tests it and tells you what changed.

Set up “Mark no-shows in Calendly for you” from your assistant

Copy the prompt above, or connect your assistant first. Free plan, no credit card.