The moment it happens

Post new Calendly bookings to Slack

When someone books, Slack shows their name, email, event type and time straight away.

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: when someone books on my Calendly, post their name, email, event type and meeting time to #bookings 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

Teams that share a Calendly link, such as a sales team using round-robin booking or a clinic with a single scheduling page, have a coordination gap. The booking lands on one person's calendar, and the others, including the person who prepared the proposal or must set up the room, learn about it only if someone remembers to tell them. A demo booked at noon for the next morning can reach the right person at 8 am.

The instant a meeting is booked, Calendly notifies ClickRuntime and a message goes to Slack with the invitee's name, the event type and the time, along with any details Calendly includes. The post appears when the booking is made, so the channel acts as a live feed of incoming meetings.

Sales teams, client services groups and clinics where a booking affects several people get the most from it.

What you get out of it

Preparation begins as soon as the meeting exists
Everyone involved sees the booking right away. The person who must prepare a proposal, set up a room or review a file has the full lead time rather than a scramble.
Round-robin teams stay in sync
When bookings are spread across several people, a shared feed shows who has what. Colleagues can offer help or cover a gap without anyone having to ask. A manager can then shift effort between channels while a campaign is still running.
Leaders see demand in real time
A visible stream of bookings shows how campaigns and outreach are working. A manager can tell within hours whether a new email sequence is producing meetings. Proportionate attention is easier when a booking is visible to the people who set priorities.
High-value prospects get noticed
If a large company or a key account books, someone senior can see it and join or prepare. Opportunities with bigger stakes receive proportionate attention. Small courtesies help invitees feel welcome, and that tends to raise attendance.
Welcome gestures become possible
A quick personal note or helpful document sent soon after booking makes the invitee feel valued. That early touch can improve the show-up rate. Shared visibility means fewer private notes and missed handovers.

How it works

What happens, step by step

When someone books a meeting with you in Calendly, ClickRuntime hears about it straight away.
It picks out the person's name and email, the event type and the meeting time.
It posts one line with those details to your #bookings Slack channel, for example "New booking: Dana Ortiz · 30 Minute Demo · 21 Oct 15:00 UTC".

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 new Calendly bookings to Slackjust nowSucceeded

Slack · #bookingsNew booking: Dana Ortiz <dana@northwind.example> · 30 Minute Demo · 2026-10-21 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.

new_booking_alert.pyexample

from clickruntime import on_event, notify

@on_event
def handle(event):
    body = event.json or {}
    if body.get("event") != "invitee.created":
        return {"posted": False}
    p = body["payload"]
    ev = p.get("scheduled_event", {})
    notify.slack(f"New booking: {p['name']} <{p['email']}> · {ev.get('name')} · {ev.get('start_time', '')[:16].replace('T', ' ')} UTC",
                 channel="#bookings")
    return {"posted": True}

FAQ

Common questions

Does it work with Calendly's round-robin and collective events?

Calendly sends an event for bookings of any type on your account, so the alert covers them. The post includes the event type, which tells the team which kind of meeting was booked and who is likely to host it.

Can I show the invitee's answers to booking questions?

Yes, if the booking form asks questions, the answers are included in the event data and can be added to the Slack message. Choose which ones to show so the post stays short but useful for the person preparing.

Is there a delay between the booking and the post?

Calendly sends the event as the booking is made, and ClickRuntime posts as it arrives. Normally the message appears within seconds. The workflow does not poll, so no schedule needs to be set. You can still adjust the message format later.

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