The moment it happens
Post rescheduled meetings to Slack
When a meeting moves, Slack shows the old and new time side by side.
- Runs
- The moment it happens
- Apps
- Calendly
- AI
- Not needed
- Access
- PAT
Send this to your assistant
Create a ClickRuntime automation: when a Calendly meeting is rescheduled, post the invitee's name with the old and new times to #bookings in Slack.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
A Calendly booking that moves is easy to overlook, because the original slot disappears and a new one appears. The team member who prepared for Tuesday at 2 pm may not see that the call has moved to Thursday, or may see an unfamiliar new booking from the same person and not realize it is the same meeting. Confusion about whether a booking is new, moved or duplicated wastes time.
When an invitee reschedules, Calendly pushes the event to ClickRuntime. If the event is a reschedule, the workflow pairs the old booking with the new one using the new_invitee link and posts a single message to Slack showing the old time and the new time together.
It suits teams that share responsibility for meetings, where colleagues depend on the time being correct.
What you get out of it
The move is clear at a glance
One message shows both the old and the new time, so nobody has to compare calendar entries. The change is understood in a few seconds. Nobody needs to compare two calendar entries or ask a colleague whether the meeting changed.
No duplicate bookings are mistaken for new demand
Pairing the old and new bookings stops a reschedule being counted or treated as a fresh meeting. Reports of new meetings stay accurate. A clean feed keeps reports on new meetings from being inflated by moved ones.
Shared calendars stay accurate
Colleagues who track the meeting in their own calendars can update them promptly. Fewer people turn up at the wrong time. Hours of preparation are used well when the date is known early.
Preparation can shift in time
Someone who prepared for a Tuesday call can move that work to match the new date, or release the time. Effort is not lost to a meeting that has simply moved.
Frequent rescheduling becomes visible
If one invitee keeps moving their meeting, the channel shows the pattern. That may signal low commitment or a scheduling problem you can address directly. Direct conversation about timing can prevent a lost opportunity.
How it works
What happens, step by step
When an invitee moves a Calendly meeting to a new time, ClickRuntime hears about it straight away.
It matches the cancelled booking with the new one, so it knows both the old time and the new time.
It posts a line to your #sales Slack channel showing who moved which meeting, from when to when.
Before it runs live
- Connect Calendly
- Paste your automation's link into the other app's webhook settings
What you get
Build your own
Need it to work differently?
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
from clickruntime import on_event, credentials, http, notify
@on_event
def handle(event):
body = event.json or {}
p = body.get("payload", {})
if body.get("event") != "invitee.canceled" or not p.get("rescheduled"):
return {"skipped": True}
h = {"Authorization": f"Bearer {credentials.secret('CALENDLY_TOKEN')}"}
new_inv = http.get(p["new_invitee"], headers=h).json()["resource"]
new_ev = http.get(new_inv["event"], headers=h).json()["resource"]
old = p["scheduled_event"]["start_time"][:16].replace("T", " ")
new = new_ev["start_time"][:16].replace("T", " ")
notify.slack(f"Rescheduled: {p['name']} moved {new_ev['name']} from {old} to {new} UTC", channel="#sales")
return {"posted": True}FAQ
Common questions
How does it match the old booking to the new one?
Does it also post when a meeting is cancelled?
Will a reschedule by the host be announced?
What permissions does it need?
Does it need AI?
How many runs does it use?
Can I change how it works?
Related
You might also like
Post new Calendly bookings to Slack
When someone books, Slack shows their name, email, event type and time straight away.
See how it worksPost Calendly cancellations to Slack
When a meeting is cancelled, you see who cancelled and their reason.
See how it worksPost Calendly no-shows to Slack
When an invitee is marked as a no-show, Slack shows who it was and which meeting they missed.
See how it worksKeep exploring
Set up “Post rescheduled meetings to Slack” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.