u/PriceNew5674

A few weeks ago, I shared a workflow that handles bookings across two courts/calendars with conflict checking. This is the next chapter.
Instead of users filling a form, I wanted an AI agent to collect booking details conversationally through chat — then pass the data into the same workflow.
Sounds simple. It wasn't.
I built a fully automated booking system for a padel club with an AI agent front-end — no code, just n8n
Padel is blowing up where I'm from and most clubs are still taking bookings over WhatsApp manually. I wanted to fix that for a 2-court setup.
Here's what I ended up with.

**What it actually does:**

\-A customer chats with an AI agent — talks naturally, no forms
\-Agent collects the details conversationally
\-Passes structured data into a booking workflow
\-Workflow checks availability, assigns the first available court, and confirms
\-Everything syncs to Google Sheets automatically
\-Works for new bookings, updates, and cancellations — including edge cases like overlapping time slots on updates

A customer types "book tomorrow at 8 for an hour" and gets a confirmed booking with an ID. That's the whole experience.

**Why I split the AI and the workflow into two separate pieces:**

Early version had the AI doing everything — checking availability, assigning courts, generating IDs. It hallucinated constantly.
The fix was simple: AI only talks to the user. The workflow handles all the logic. The agent calls the workflow like a tool, gets a result back, and translates it into a friendly reply.
Much more reliable. Much easier to debug when something goes wrong.

**The core insight:**

Keep AI in the conversation layer. Keep deterministic logic in the workflow layer. When I mixed them, things broke in ways that were hard to debug. When I separated them, both parts became much easier to reason about and fix.

**What this could work for beyond padel:**

Any multi-resource booking scenario — tennis courts, meeting rooms, recording studios, parking bays. The core pattern (AI conversation layer → deterministic booking backend → calendar + sheets sync) is reusable.

Full workflow is on GitHub if anyone wants to dig into it or adapt it for their own use case. Happy to answer questions or help anyone trying to build something similar.
https://github.com/rajakumarbakhtawar-dotcom/padel-test-2-courts/issues/1#issue-4736136194

**Curious what others are doing:**

If you're using AI agents with n8n tools — how much logic are you putting in the prompt vs the workflow?
And how are you handling ambiguous user input before it reaches your tools?

Most “AI booking systems” sound impressive until they double-book someone or confirm a slot that doesn’t exist.

So I tried building something that does the opposite.

This is my first serious n8n workflow, and the goal was simple on paper:
Book a slot across two separate calendars without ever making a wrong decision.

In reality, it turned into a full-blown logic system.

---

What it actually does:

- Takes a booking request (date, time, user info)
- Checks Calendar A in real-time
- If free → books instantly
- If not → checks Calendar B
- If free → books there instead
- If both are full → returns a clean “not available” (no guessing, no fake confirmations)

---

What makes this different:

This isn’t just “if-else” logic slapped together.

The workflow:

- Verifies availability before every action
- Handles fallbacks automatically
- Supports updates, cancellations, and re-booking flows
- Syncs everything into Google Sheets for tracking
- Has explicit failure paths (so nothing silently breaks)

End result:
No double bookings
No race conditions
No hallucinated confirmations

Just deterministic outcomes.

---

Why I built it this way:

Because AI alone is unreliable for execution.

You can have the smartest chatbot in the world —
if it guesses availability, it’s useless in production.

So I’m separating concerns:

- AI = conversation layer
- Workflow = decision + execution layer

---

What I’m adding next:

I’m now plugging in an AI agent that will:

- Talk to users on WhatsApp / Telegram
- Collect booking details naturally
- Pass structured data into this workflow
- Let the workflow handle the actual booking logic

So the AI never decides anything critical — it just gathers input.

---

Where this gets interesting:

This pattern works anywhere you have parallel resources:

- Padel / tennis clubs (multiple courts)
- Cinemas (multiple halls)
- Restaurants (tables, sections, branches)
- Clinics, salons, rentals — anything with slots

---

The bigger idea:

Instead of “AI that tries to do everything,” this is:

AI for interaction + workflows for truth

And that combination feels way more production-ready.

---

Still early, but this is the first version that actually feels reliable enough to sell.

Curious if others here are structuring AI systems this way —
or still letting agents handle everything end-to-end.