AI chatbot call center: Taxi booking support (production-ready, part 7)

Workflow Name: 🫶 Taxi Booking Support Template was created in n8n v1.90.2 Skill Level: Mid Categories: n8n, Chatbot Stacks - Schedule Trigger node - Postgres node - AI Agent node - Google Calendar node - Execute Sub-workflow - If node, Switch node, Code node, Edit Fields (Set) Prerequisite - Sub-workflow: Demo Call Back (or your own node) Production Features - Scaling Design for n8n Queue mode in production environment - Customize Expired Booking Actions example - Multi-Language Design What this workflow does? This is a n8n Taxi Booking Support, the background node to process the job at scheduled. It is scheduled to check the database for outstanding booking and handle the after sales process. In this particular case, it will check for OPEN booking over 10 minutes, then update the booking status from OPEN to CANCELLED, delete the Calendar event and send a reply to the user. How it works - The Schedule Trigger node is scheduled to run every 5 minutes. - It will check the database for OPEN or HOLD booking. - For OPEN booking - update the booking status to CANCELLED - delete the Calendar event - send a reply to the user - Optional: The AI Agent is used to create the reply message to the user in Multi-language based on the language set in the booking. Set up instructions 1. Pull and Set up the required SQL from our Github repository. 2. Create you Postgres credentials, refer to n8n integration documentation for more information. 3. Select your Credentials in Open Hold Booking and Set Cancel Booking. 4. Create your Google Calendar credentials, refer to n8n integration documentation for more information. 5. Create a Google Calendar, e.g. DEMO 6. Select your Credentials in Delete Event, and select the above Calendar 7. Remember to activate this workflow for schedule to run. How to adjust it to your needs 1. There should be more status for the booking. 2. The current action only check for OPEN and HOLD booking, you can do more based on your needs. 3. You can replace the sub-workflow trigger Call Back to another flow as needs.