← Back to library

Confirm padel court times from a chat channel

u/PriceNew5674 automated bookings in n8n for a padel venue with two courts that still took WhatsApp bookings by hand. A chat agent collects details from natural messages, then calls a separate booking workflow that looks up open slots, gives the first open court, confirms with a booking ID and syncs to Google Sheets. An earlier all-AI version kept hallucinating.

  • OutcomeCustomers book, change or cancel courts by chatting, while a deterministic workflow assigns courts and prevents clashes.
  • SetupAn afternoon+
  • LevelIntermediate
  • Creditu/PriceNew5674 on r/n8n
View original
Works with
ChatGPTn8n

Published Oct 23, 2026Updated Oct 23, 2026AI dry run on sample input: passed Oct 23, 2026Source verified Oct 23, 2026

When should you use it?

  • You rent courts, rooms, studios or bays that are booked by message
  • Your chatbot sometimes invents availability
  • You want booking rules you can debug

Not for: Single-resource bookings a simple booking page already handles; Payments, unless you add a proper payment step

What do you need, and what do you get?

You need

  • A chat channel and an agent node
  • A booking workflow with your resources and calendars
  • A sheet or database for bookings

You get

  • Confirmed bookings with IDs
  • Correct handling of updates, cancellations and overlaps
  • A synced booking sheet

How does it work, step by step?

  1. Separate talk from logicLet the AI only collect details and phrase replies; keep availability and assignment in a workflow.
  2. Define the booking contractSpecify the exact fields the agent must pass: date, start, duration, name, and booking ID for changes.
  3. Assign deterministicallyCheck each court's calendar and give the first free one, rejecting overlaps.
  4. Handle edits carefullyFor updates, exclude the booking's own slot when checking clashes.
  5. Translate the resultHave the agent turn the workflow's response into a friendly confirmation with the ID.

The prompt

Our own prompt, inspired by u/PriceNew5674 on r/n8n and written to work in ChatGPT and n8n. Values in lime are placeholders.

Fill in the blanks (optional; the copied prompt uses your values)

Prompt2 variables
You collect court bookings by chat for {club}. Gather: date, start time, duration, customer name, and for changes the booking ID. If any field is unclear (for example 'evening'), ask one short question. When complete, call {booking_tool} with exactly these fields and nothing else. Never say a court is free or assign one yourself; report only what the tool returns, including the booking ID. If the tool reports a clash, offer the alternatives it returns.

Inspired by u/PriceNew5674 on r/n8n: I added an AI agent to my n8n booking workflow — here's what I learned separating "conversation" from "logic". The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.

What can go wrong?

  • Ambiguous phrases like 'tomorrow evening' need clarification before the tool is called.
  • Updates that overlap their own old slot are a classic bug; test them.

Our take

The core lesson in this post applies to almost every agent that touches real resources: keep the model in the conversation and keep decisions in code. When the AI was checking availability and assigning courts, it made things up; when it only gathered details and called a workflow, the system became reliable and debuggable. That split also makes the agent easy to reuse, since the booking logic doesn't change if you swap the chat channel or the model. Spend your effort on the contract between the two layers: exactly which fields the agent must collect, what the workflow returns, and what happens when input is ambiguous. Test the awkward cases deliberately, like moving a booking by thirty minutes so it overlaps itself, or two people requesting the same slot at once. The author's examples beyond padel, meeting rooms, studios and parking bays, are realistic, because the backend doesn't care what the resource is.

Where the time goes back: Bookings that staff handled message by message are confirmed automatically and correctly.

FAQ

Why not let the AI check availability?
He says it hallucinated constantly when it handled logic; moving logic into the workflow fixed that.
Is the workflow public?
He links it from a GitHub issue in the post.

Source and credit

Inspired by u/PriceNew5674 on r/n8n. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.

Inspired by
I added an AI agent to my n8n booking workflow — here's what I learned separating "conversation" from "logic"
Creator
u/PriceNew5674 on r/n8n
Published on
Reddit
Original date
Oct 23, 2026
License
Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
Originally for
ChatGPT
AI dry run
Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS (desk check, not a live run in the vendor's app). Replaces an earlier templated dry-run note.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails.
Verified
Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.

Are you the creator? Claim or correct this page.

More in Operations & Admin

All 203 Operations & Admin playbooks →

Related playbooks

Operations & AdminWorkflow✓ AI dry run

Confirm tables on WhatsApp against a live book

Guests book a table by chatting on WhatsApp, staff see bookings on a table plan, and reminders go out automatically.

Credit: u/begylewis on r/micro_saas

An afternoon+
Operations & AdminWorkflow✓ AI dry run

Gate after-hours dental phone triage and booking

Calls are answered and booked against the real schedule, emergencies reach the dentist, and reminders and recalls run without front-desk time.

Credit: u/anassy1 on r/AiAutomations

An afternoon+
Operations & AdminWorkflow✓ AI dry run

Log every agent action as ok, failed or unknown

Give each write an agent makes one structured log line with its attempt ID, request key, an outcome of ok, failed or unknown, and what the agent did next, then keep one saved query for the combination that should never happen, an unknown outcome the agent confirmed to the customer, so a repeat of the incident shows up in minutes.

Credit: ccch713

Under an hour
Operations & AdminSkill✓ AI dry run

Write an NCR that scopes and locates every suspect part

Use the ncr-writeup skill from Anthropic's Claude for Manufacturing plugin to turn an inspector's finding or a customer complaint into a nonconformance report that records the measured condition, cites the exact requirement at the revision the part was built to, works out how many parts are suspect and why, checks all five places they could be, searches earlier reports for the same problem and drafts a customer notice when bad parts may have shipped.

Credit: anthropics

Under an hour
Operations & AdminWorkflow✓ AI dry run

Test a phone agent on one scripted call before rollout

Run every phone agent through the same awkward booking call with fixed traps before you let it dial real businesses.

Credit: u/Evening_Hawk_7470 on r/AI_Agents

Under an hour