AI Chatbot Call Center: Taxi Booking Worker (Production-Ready, Part 5) - n8n Workflow | Neura Market
AI Chatbot Call Center: Taxi Booking Worker (Production-Ready, Part 5)
### Workflow Name: ☍♒⚏ Taxi Booking Worker
Template was created in n8n v1.90.2
### Skill Level: High
### Categories: n8n, Chatbot
### Stacks
- Execute Sub-workflow trigger node
- Chat trigger node
- Redis node
- Postgres node
- Google Calendar node
- Execute Sub-workflow
- If node, Switch node, Code node, Edit Fields (Set)
### Prerequisite
- Execute Sub-workflow trigger: **Call In Center** (or your own node)
- Sub-workflow: **Demo Call Back** (or your own node)
# Production Features
- **Scaling Design** for n8n **Queue mode** in production environment
- Customize **Open Booking Action**
- Integrate with **Long Term Memory** backup.
- **Error Management**
# What this workflow does?
This is a n8n **Taxi Booking Worker**, the worker node to process the job. It will wait for a message from the Call Center node and handle the real process here. In this particular case, it will check the input number for the selected provider, then update the booking from NEW to OPEN, then clean up the orphan data.
# **How it works**
- The **Form Trigger** node will wait for the message from any node with the input in number.
- First check for NEW booking under the same chat session
- For input 0, which is cancel - Reset the user session in Redis memory
- For input 1 or above, which is the provider selection number - Set the booking status to OPEN in database - OPTIONAL Save the summary to **User Memory** database - OPTIONAL Create a new Event in **Google Calendar** and sync to the database - Reset the user session in Redis memory
- Afterward, process data clean up - Delete the provider selection number queue in Redis - Delete the route data in Redis - OPTIONAL Delete the chat memory with current session
- Finally, output the response to the **Call Back** node
# **Set up instructions**
1. Pull and Set up the required SQL from our [Github repository](https://github.com/ChatPayLabs/n8n-chatbot-core).
2. Create your **Postgres credentials**, refer to [n8n integration documentation](https://docs.n8n.io/integrations/builtin/credentials/slack/?utm_source=n8n_app&utm_medium=credential_settings&utm_campaign=create_new_credentials_modal) for more information.
3. Select your Credentials in **Booking, Set Open Booking, Sync Booking Google Cal**, and **Save User Memory**.
4. Create your **Redis credentials**, refer to [n8n integration documentation](https://docs.n8n.io/integrations/builtin/credentials/slack/?utm_source=n8n_app&utm_medium=credential_settings&utm_campaign=create_new_credentials_modal) for more information.
5. Select your Credentials in **Reset Session, Reset Session 2**, **Delete Provider Number** and **Delete Route Data**.
6. Create your **Google Calendar credentials**, refer to [n8n integration documentation](https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.googlecalendar/?utm_source=n8n_app&utm_medium=node_settings_modal-credential_link&utm_campaign=n8n-nodes-base.googleCalendar) for more information.
7. Create a Google Calendar, e.g., DEMO
8. Select your Credentials in **Create Event**, and select the above Calendar
9. FOR TESTS ONLY. Enable the **Telegram Test Output** for testing from the **Test Input**.
# How to adjust it to your needs
1. You can specify a number to trigger the specific action based on your needs.
2. The current action only creates an event in Google Calendar, you can do more based on your needs.
3. You can replace the sub-workflow trigger **Flow Trigger** and **Call Back** to another flow as needs.
Platform
n8n
Category
Communication
Price
Free
Creator
ChatPayLabs
Agent
DEMO
if
set
redis
switch
postgres
stickyNote
googleCalendar
executeWorkflow
How to import this workflow into n8n
1Purchase or download the workflow to get the n8n workflow JSON file.
2In your n8n instance, open Workflows and choose "Import from File" (or paste the JSON with Ctrl+V on the canvas).
3Open each node marked with a credential warning and connect your own accounts and API keys.
4Run the workflow once manually to verify the data flow, then toggle it to Active.