Skip to content
Agentguiden.no
Submit your own

The agent talks, the n8n flow assigns the court

The author put a chat agent in front of an n8n flow for a padel club with 2 courts. The sentence book tomorrow at 8 for an hour is supposed to return a confirmed booking with an ID. When the agent assigned courts itself, it hallucinated. Now the agent talks, and the flow does the logic.

Done with n8nAdvanced

This is a public report, not advice from Skatteetaten, NAV, Altinn or an accountant. Check figures, deadlines and decisions against the original.

What was done

On 01 July 2026 the author writes that he added an agent to an n8n flow that books two courts and checks conflicts. The club is a padel club with 2 courts. The customer chats, with no form. The agent collects the details and passes structured data to the flow. The flow checks availability, takes the first free court and confirms. Everything is written to Google Sheets. The flow handles new bookings, changes and cancellations, including overlap when a slot is moved. He describes the experience like this: a customer types book tomorrow at 8 for an hour and gets a confirmed booking with an ID. At first the agent also did availability, court assignment and IDs. It hallucinated. He split the layers. The agent only talks. The flow does the logic. The agent calls the flow as a tool, gets a result and translates it.

How it went

Availability and the court sit in the flow, after the agent hallucinated when it did that itself. He describes a confirmed booking with an ID for the sentence at 8. The customer is not named.

Worth knowing

The sentence about tomorrow at 8 is how he describes the experience, not a named customer. The club is not named. He does not say a cancellation has actually been run. Check the original. This is not a finished booking for another club.

How to do it

  1. Let the agent only collect time, duration and name, and pass that to the flow.
  2. Let the flow check availability and conflicts, and return an answer the agent can read back.
  3. Confirm, change or cancel only after you have seen the answer from the flow.

Try it with n8n

Take a booking for [court] at [time]. Check availability in the flow, not in the chat. Do not confirm, do not change and do not cancel until I say yes.

Replace text in brackets with your own.

Done when. The answer from the flow has been read, and no booking has been confirmed without a yes.

Safety rule. No confirmation, change or cancellation until you have said yes.

Read the original

Read the original · u/PriceNew5674 on Reddit ·

More examples

  • The print file failed, the sites went up

    u/TheRealOctaneGuy had Manus design labels. The rendering was usable, the print file was not. He drew the file himself. He writes that he has launched 7 sites, and that a screenshot of a testimonial is added by Manus.

    ManusNewreddit.com

  • Email and stock for a wholesaler in Dallas

    He set up flows for a food wholesaler in Dallas, Texas. A ChatGPT project writes short email. After 4 months he writes that revenue went from about $22K to around $45K a month.

    ChatGPTNewreddit.com

  • The enquiry becomes a task, the reply goes through Telegram

    Toma built an n8n setup for customer enquiries. It creates a ClickUp task and notifies him on Telegram. He replies there himself. The agent can send email, update the status or close the thread from his reply.

    n8nNewx.com

  • One tenant message became two jobs

    The author had an agent read tenant messages, split them by trade and send the jobs. It handles about two hundred messages a month and saves the operations manager close to fifteen hours a week. For a shop with a fixed reorder at 200 units he did not use an agent.

    Valgfri agentNewreddit.com

Five agents a day

A short daily email with five concrete examples of AI agents. Nothing else.