Zero Duplicate Bookings Since: A Dental Clinic's Booking Agent Logs Every Write as OK, Failed or Unknown and Sends Unknowns to a Human
- Level Advanced
- Setup1–3 hrs (estimated)
- Evidence Some evidence
- CostNot stated in source
- No-codeNo
What did they do with n8n?
A dental-clinic booking agent (chat plus scheduled jobs) had booked a patient more than once after a timeout. The fix was a logging rule: every tool call that writes something logs exactly one outcome, ok, failed or unknown, plus the attempt ID, an idempotency key and what the agent did next. A timeout counts as unknown, and unknowns go to a human task instead of an automatic retry, because retrying an unknown is how one booking becomes three. A test fires the same key twice and checks only one booking is made; it has caught two unrelated regressions so far. No patient data or chat content is logged, and there have been zero duplicate bookings since.
How it went
n8n community 'Built with n8n' post by @ccch713 (Nov 10, 2026 UTC), follow-up to a duplicate-bookings incident at a dental-clinic booking agent: ok/failed/unknown outcomes, idempotency keys, unknowns routed to human escalation, an acceptance test that fires the same key twice and has caught two unrelated regressions; zero duplicate bookings since. The author's signature links his open-source GitHub project
Worth knowing
- n8n community 'Built with n8n' post by @ccch713 (Nov 10, 2026 UTC), follow-up to a duplicate-bookings incident at a dental-clinic booking agent: ok/failed/unknown outcomes, idempotency keys, unknowns routed to human escalation, an acceptance test that fires the same key twice and has caught two unrelated regressions; zero duplicate bookings since. The author's signature links his open-source GitHub project.
Prompt
Core command is original; setup is cleaned from the source.
Review my n8n booking workflow [workflow name]. Before every step that creates or changes a booking, add a sub-workflow that writes one log line with an attempt ID, an idempotency key, and the outcome: ok, failed or unknown (treat any timeout as unknown). Route unknown outcomes to a human task in [tool], never to Retry On Fail. Add a test workflow that sends the same idempotency key twice and confirms only one booking is created. Don't log any patient details or chat content.
Recommended
Try it in Grok Bot
- Copy the prompt (button below).
- Open Grok Bot chat and paste it. Replace any [bracketed] placeholders.
- Connect the listed tools (as needed) as connectors when Grok Bot asks.
- If the task repeats, ask: "Make this a daily routine."
Alternatives: the same prompt works in n8n, Claude, ChatGPT Agent, OpenClaw.
Set it up
Stack: n8n
- Read the original source for full context.
- Connect the tools your agent needs.
- Paste the prompt and replace [bracketed] placeholders.
- Run once manually and check the output before scheduling it.
Generic suggested steps, not from the source.
Evidence
n8n community 'Built with n8n' post by @ccch713 (Nov 10, 2026 UTC), follow-up to a duplicate-bookings incident at a dental-clinic booking agent: ok/failed/unknown outcomes, idempotency keys, unknowns routed to human escalation, an acceptance test that fires the same key twice and has caught two unrelated regressions; zero duplicate bookings since. The author's signature links his open-source GitHub project (as of 2026-11-12)
Source: Web · Verified by us: not yet · Report broken or outdated