When should you use it?
- An agent books, cancels or changes appointments, orders or payments through a tool or API
- Your workflow retries failed calls automatically, or the platform does it for you
- Customers have ever received two confirmations, two invoices or two bookings for one request
Not for: Read-only agents that only look things up, where a repeated call does no harm; Booking systems with no way to attach a request ID or look up an existing booking; Teams that cannot staff the hand-off when the agent says a person will confirm
What do you need, and what do you get?
You need
- The agent's booking, cancel and change tools and how each one reports success
- A way to build a stable key per request, such as patient, slot and conversation ID
- Somewhere to send uncertain cases for a person to confirm
- A test setup where you can force a tool call to time out
You get
- A rule in the agent's instructions that a timeout or empty reply is never confirmed to the customer
- Write actions that carry a request key, so a repeat changes nothing
- A hand-off message and a queue of unconfirmed bookings for staff
- A permanent forced-timeout acceptance test that runs on every change
How does it work, step by step?
- List every write toolWrite down each tool that creates, changes or cancels something, and what a success, a failure and a timeout look like for each.
- Add a request keyBuild one key from the details that make a booking unique and send it with every write, so the booking system can ignore a repeat.
- Rewrite the success ruleTell the agent that only an explicit success reply counts, and that a timeout means it must say a person will confirm.
- Route the unknownsSend every unconfirmed request to a staff queue with the key, so someone checks the calendar before calling the customer.
- Make the timeout test permanentForce one booking call to time out in a test run, check there is one booking and an honest reply, and rerun that test whenever the workflow changes.
The prompt
Our own prompt, inspired by ccch713 and written to work in n8n, Custom agent, ChatGPT and others. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
You book appointments for {business_name} using the {booking_tool} tool. Every booking, change or cancel call must include request_key = {customer_id}-{slot}-{conversation_id}. Treat a call as successful only when the tool returns an explicit confirmation with a booking ID. If the tool times out, errors or returns nothing, do not tell the customer they are booked. Say: "I've passed this to our team to confirm and they will message you shortly." Then add the request to {staff_queue} with the request key. Never retry a write with a new key, and never call the booking tool twice for the same request on your own.
Inspired by ccch713: n8n Community: duplicate bookings after a tool timeout. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Raising the timeout only hides the problem until the next slow day, and the agent still cannot tell what happened.
- Turning retries off swaps a double booking for a lost one. Keep retries, but make repeats harmless.
- An instruction to keep trying until it works is how one request becomes three appointments.
- A request key built from the timestamp of each attempt changes on every retry, so it protects nothing. Build it from the request, not the attempt.
Our take
This is a short post with an unusually clear lesson: the dangerous failure in an agent workflow is not the error, it is the moment the agent cannot tell whether its action happened. The clinic's agent filled that gap the way language models tend to, by sounding confident, and a background retry turned that confidence into a second appointment. We like that the author lists the tempting wrong fixes, because each one is what most teams try first: a longer timeout, no retries, or an instruction to keep trying. The real fix has two halves that need each other. The agent must treat silence as unknown and hand off, and the system must make a repeated write harmless with a request key. Either half alone still leaves a hole. The part we would copy first is the permanent forced-timeout test, because it is cheap to build and keeps protecting you after the people who remember the incident move on. In our dry run with a fictional physiotherapy clinic, a forced timeout produced one booking, an honest hand-off reply and a queue item for staff.
Where the time goes back: One honest hand-off message costs a staff member a minute, while a double booking costs a phone call, a cancellation, an empty chair and some trust.
FAQ
Is this specific to n8n?
What is a request key in plain terms?
Did the change work?
Source and credit
Inspired by ccch713. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- n8n Community: duplicate bookings after a tool timeout
- Creator
- ccch713
- Published on
- n8n Community
- Original date
- Nov 9, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- n8n
- AI dry run
- Nov 9, 2026: passed. Dry-run tested by our AI test agent on sample input. Forced timeout: one booking with the key (two without), honest hand-off reply, staff queue item created.
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
- Nov 9, 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.