The moment it happens

Post Calendly no-shows to Slack

When an invitee is marked as a no-show, Slack shows who it was and which meeting they missed.

Runs: The moment it happens
Apps: Calendly
AI: Not needed
Access: PAT (webhooks need paid plan)

Send this to your assistant

Create a ClickRuntime automation: whenever someone is marked as a no-show in Calendly, post their name, email and the meeting to #sales in Slack.

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

Add to ChatGPT Add to Claude

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

Why use it

Why teams use this automation

When an invitee does not join a Calendly meeting, the host often waits ten minutes, then marks it a no-show and moves on, without telling anyone. The sales manager never learns that the demo did not happen, the follow-up sequence that assumes the meeting took place goes out anyway and the prospect receives a thank-you note for a call they skipped.

When Calendly records an invitee as a no-show, it sends an event to ClickRuntime. The workflow looks up the invitee and the event to see who it was and when, then posts the details to Slack. The team knows right away that the meeting did not happen, and can act on that information.

It suits sales and service teams who run follow-up processes that depend on whether the meeting happened.

What you get out of it

Follow-up reflects what really happened
A no-show needs a different message than a completed call. Hearing about it quickly prevents embarrassing thank-you emails and lets you offer a new time instead. The right message depends on what happened, and the alert makes that obvious right away.
Managers see attendance quality
A shared feed of no-shows shows which lead sources, event types or reps suffer most. Improvement efforts can then target the real problem. That pattern can show which lead sources or event types deserve different handling.
Pipeline forecasts stay honest
Opportunities that are credited with a first meeting but never had one distort a forecast. Marking and announcing no-shows keeps stages accurate. A forecast built on actual meetings rather than scheduled ones is far more reliable for planning.
Recovery attempts start fast
A friendly reschedule message sent within the hour tends to be received better than one sent days later. Many no-shows are simple forgetfulness and are easily rescued. Offering a new slot quickly shows that you still care about the conversation.
Reminder strategy can be tested
If no-shows cluster on a certain day or time, the channel makes it visible. You can then try an earlier reminder or a different slot and see the effect. Small experiments with timing can measurably raise the share of invitees who attend.

How it works

What happens, step by step

When an invitee is marked as a no-show in Calendly, ClickRuntime hears about it straight away.
It looks up the person's name and email and the meeting they missed, including its time.
It posts a line to your #sales Slack channel, such as "No-show: Jordan Park missed Product demo at 15:00 UTC", so someone can follow up.

Before it runs live

Connect Calendly
Paste your automation's link into the other app's webhook settings

What you get

RunsThe moment it happens

Post Calendly no-shows to Slackjust nowSucceeded

Slack · #salesNo-show: Jordan Park (jordan@acme.io) missed Product demo at 2026-10-19 15:00 UTC

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

Act only on the items that match your own rules, and skip the rest
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.

no_show_alert.pyexample

from clickruntime import on_event, credentials, http, notify

@on_event
def handle(event):
    if event.json.get("event") != "invitee_no_show.created":
        return {"skipped": True}
    h = {"Authorization": f"Bearer {credentials.secret('CALENDLY_TOKEN')}"}
    invitee = http.get(event.json["payload"]["invitee"], headers=h).json()["resource"]
    meeting = http.get(invitee["event"], headers=h).json()["resource"]
    notify.slack(
        f"No-show: {invitee['name']} ({invitee['email']}) missed {meeting['name']} at {meeting['start_time'][:16].replace('T', ' ')} UTC",
        channel="#sales",
    )
    return {"posted": True}

FAQ

Common questions

Who marks the invitee as a no-show in Calendly?

The host or an automation marks the invitee in Calendly, which then sends the no-show event. This alert reacts to that mark, so it appears only after the no-show has been recorded. A separate hourly workflow can mark them automatically.

Does the alert include contact details?

It includes what the lookup returns for the invitee and event, such as name, email and event time, depending on what Calendly provides. That is enough for a follow-up message to be sent from your own mail or CRM.

Can no-show alerts go to different channels by event type?

Yes. Because the alert knows which event the invitee missed, a rule can send sales demos to the sales channel and support calls to another. Describe the routing in chat and confirm it. Each route is shown to you before it starts.

What permissions does it need?

PAT (webhooks need paid plan). 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 for each event the app sends.

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.

The moment it happens