A customer books an appointment in the conversation
A request in plain words becomes an event in your calendar.
What the scenario looks like
- Execute + Data
- LLM
- Data
Booking an appointment is three messages and one mistake: the customer names a time, a human checks it back, then copies it into the calendar and occasionally forgets. Here there is nothing between the request and the event.
What is inside
- A request to book — the entry.
- When and what for — the model turns “tomorrow at three” into a concrete start and end. Today’s date comes from the run: without it the model picks a date out of its head.
- Calendar — the connection node.
- Write to the calendar creates the event.
- Confirmation answers the customer.
This is the only scenario that changes an external system
A mistake here costs more than a typo in an answer: a misread “on Friday” becomes a meeting in your calendar, and you are the one who deletes it. Start with a separate calendar for bot bookings — then a wrong entry is visible and not mixed in with the real ones.
What is missing here: an availability check. The scenario books the time it was given without asking whether it is free. Free slots are worked out by “The bot tells a customer when you are free” — put that before this step if the bot runs without you.
What to set up for yourself
- The time zone on the write node.
- The default duration. The prompt adds an hour when the customer does not say.
- The event title. Currently the topic plus the customer’s name, so the calendar shows who you are seeing without opening the event.
What to connect
A calendar over CalDAV, and the connection needs write access. Check that before publishing: read access is given away easily, while write access on some providers needs its own app password.