Cal.com solves the problem of agreeing on a time. But once a booking exists, a string of chores usually follows:
- Adding this person to your customer list
- Sending them the material they should read beforehand
- Digging up their background for yourself before the meeting
These three are the same every time, and every time you do them by hand. That is exactly what webhooks are for.
30-second overview
| Item | Details |
|---|---|
| What it solves | The chores that follow a confirmed booking |
| How it connects | A Cal.com webhook firing into n8n |
| The most valuable piece | An automatic briefing before the meeting |
| Most often missed | Not handling cancellation and reschedule events |
| When it is not worth it | Two or three bookings a week |
How to connect them
Cal.com can send a webhook when a booking is made, rescheduled or cancelled. Create a Webhook node in n8n, take the URL it gives you, paste it back into Cal.com, and you are connected.
From then on every booking arrives in n8n with the full payload — who booked, what time, which event type, and whatever they filled in on the form.
Three things worth automating
1. Write them into your customer list
The booker's details go straight into NocoDB or your CRM, with nothing to backfill later.
The important part is to record which event type they booked while you are at it — someone booking "product consultation" and someone booking "post-sales support" want completely different things, and that field pays off later.
2. Send different prep material per event type
Cal.com's confirmation email is generic. But if someone booked a product demo you might want to attach the spec sheet, and if they booked technical support you want to ask for their environment details up front.
Use an IF node in n8n to branch on the event type and send different content. This makes you look thoroughly prepared while you did nothing at all.
3. Brief yourself automatically before the meeting
Set up a schedule that gathers this person's details an hour before the meeting and pushes them to you — what they wrote in the form, how many times they have booked before, what you discussed last time.
This is the most valuable of the three, because it solves the problem of only remembering to prepare three minutes before the meeting starts.
Do not forget cancellations and reschedules
Most people only handle "booking created", and then their list fills up with meetings that were actually cancelled.
Handle the cancellation and reschedule webhooks too, at least to write the status back. Skip this and your customer list is unusable within a couple of months.
When it is not worth doing
Let us be honest: if you only get two or three bookings a week, doing it by hand is faster. Building this workflow takes an hour or two, on top of n8n's subscription (avg. NT$499/mo, billed yearly), and at low volume that does not pay off.
The signals that it is worth it: bookings reach ten a week or more, or you keep forgetting to send prep material, or you want to know "which event types did this month's bookings come from" and there is nowhere to look it up.
There is another reason people underestimate — the workflow keeps running while you are away. Someone books during your holiday, the data still lands in the system and the prep email still goes out, with nothing to catch up on when you get back.
Start with the one you will feel most
You do not have to build all three at once. Do the pre-meeting briefing first, because you feel its effect on day one.
The value of the other two (writing to the list, sending prep material) takes a while to accumulate, and they need you to think through your data structure first. Starting with the one that pays off immediately makes it much easier to stay motivated and finish the rest.
Handling cancellations and reschedules
If you handle bookings but not cancellations, your list slowly turns into data you cannot trust. At minimum, write the status back when something is cancelled.
A more advanced version fires a notification to you on cancellation — when the same customer cancels twice in a row, that is usually a signal worth noticing.
How to build the three in practice
1. Write them into your customer list
The booker's details go straight into a table, with nothing to backfill. Record which event type they booked while you are at it — someone booking "product consultation" and someone booking "post-sales support" want completely different things, and that field pays off later.
2. Send different prep material per event type
Cal.com's confirmation email is generic. Use a conditional node to branch on the event type and send different content — the spec sheet for a product demo, a request for environment details for technical support.
This makes you look thoroughly prepared while you did nothing at all.
3. Brief yourself automatically before the meeting
Set up a schedule that pushes you a tidy summary an hour before the meeting: what they wrote in the form, how many times they have booked before, what you discussed last time.
This is the most valuable of the three, because it solves the problem of only remembering to prepare three minutes before the meeting starts.
FAQ
Q: Which events should I handle?
At least three: booking created, cancelled, rescheduled. Most people only handle the first, and then the list fills with meetings that were actually cancelled and is unusable within a couple of months.
Q: Where should the data live?
NocoDB or whatever system you already run both work. The advantage of NocoDB is that data changes can trigger workflows in the other direction; see n8n plus NocoDB.
Q: What volume makes it worthwhile?
Building the workflow takes an hour or two, plus the n8n subscription. It starts paying off past ten bookings a week, or whenever you keep forgetting to send prep material.
Q: What happens while I am on holiday?
The workflow keeps running. Data still lands in the system, prep emails still go out, and there is nothing to catch up on — a benefit many people underestimate.
Q: Can I reply to customers automatically?
You can, but be careful. Automatic replies backfire easily when the other person expects a human, so start with things that are obviously the system talking, like sending material.
Do not start by auto-replying to customers
Technically you can send a "personalized" email automatically once a booking is made. But a warning: automatic replies backfire easily when the other person expects a human.
The safer order is to start with things that are obviously the system talking — sending material, sending reminders, sending what-to-expect notes. The recipient knows these are automated, so there is no gap between expectation and reality.
Once you are sure the content is genuinely useful, you can make the tone more human. Do it the other way around and the very first email feels like a brush-off.
Confirm the webhook is really firing
Once it is set up, book a slot yourself and watch. Cal.com showing "sent" does not mean n8n received it — a wrong URL or an inactive workflow both fail silently. It is only really connected once you see that run in the n8n execution log.
Sources and further reading
For Cal.com features and plans, the official announcements are authoritative:
Further reading
- Cal.com Tutorial: Setting Availability and Connecting Google Calendar
- n8n Webhooks and Third-Party Integrations
- n8n Plus NocoDB: Keep Your Automation Data in Your Own Hands
- Cal.com Self-Hosted vs. Managed: The Real Cost Is Integration, Not Servers
- RoamerHost managed Cal.com plans
- RoamerHost managed n8n plans
Want someone to do it for you?
If you would rather not build these workflows yourself, or the scale calls for someone to plan it with you, Roamer Tech (the company behind RoamerHost) takes on business process automation and custom AI agent projects:
