The moment it happens
Post Calendly routing form answers to Slack
Every routing form answer reaches Slack, along with whether the person went on to book.
- Runs
- The moment it happens
- Apps
- Calendly
- AI
- Not needed
- Access
- PAT (paid plan with routing forms)
Send this to your assistant
Create a ClickRuntime automation: when someone submits my Calendly routing form, post their answers and whether they booked a meeting to #leads in Slack.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
A Calendly routing form asks visitors a few questions before deciding who they should meet, or whether they should book at all. A visitor who answers that they have a team of 200 people and a budget in place might never actually book, because they are routed to a page they do not like or get distracted. Those answers are valuable leads, yet if no booking follows, nobody sees them.
Whenever a routing form is submitted, Calendly pings ClickRuntime. The workflow formats the questions and answers into a readable list and posts them to Slack, whether or not the person goes on to book. Your team sees the intent as it appears, rather than only the bookings that complete.
It suits teams that qualify inbound interest with a routing form, including sales and partner teams.
What you get out of it
Interest is captured even without a booking
Visitors who answer but do not book still leave their details with you. A follow-up from a person turns some of them into meetings that would never have happened. Even partial interest is worth a short, personal reply.
High-intent answers get priority
A large company or a stated budget stands out in a channel read by sales. The best leads are seen before the less promising ones. Leaders can see at a glance whether the form is working as designed.
The form's effectiveness is easy to judge
Seeing submissions next to actual bookings shows how many people drop out. If many answer but few book, the routing or the next page may need rework. Speed of response is one of the biggest drivers of whether a lead becomes a conversation.
Sales can react while interest is fresh
Contacting a visitor within minutes of submission is far more effective than waiting. They are still at their desk, still thinking about the problem. Real answers are the best guide for deciding which questions to keep.
Questions can be refined with evidence
Reading real answers in the channel tells you which questions produce useful information and which are ignored. You can improve the form using actual responses. Small edits to the form can then be tested against real responses.
How it works
What happens, step by step
When someone fills in one of your Calendly routing forms, ClickRuntime hears about it straight away.
It lays out each question with the person's answer, and notes whether they went on to book a meeting.
The answers are posted to your #sales Slack channel, so the team can see who is interested and what they need.
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, notify
@on_event
def handle(event):
body = event.json or {}
if body.get("event") != "routing_form_submission.created":
return {"skipped": True}
sub = body["payload"]
qa = "\n".join(f"• {q['question']}: {q['answer']}" for q in sub.get("questions_and_answers", []))
booked = "booked a meeting" if sub.get("submitter") else "did not book"
notify.slack(f"New routing form answer ({booked}):\n{qa}", channel="#sales")
return {"posted": True}FAQ
Common questions
Does a routing form submission include the visitor's email?
Does it post for people who then book a meeting?
Can I hide some answers from the Slack message?
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 Calendly routing form answers to Slack” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.