Skip to main content

AI chatbot call center: Taxi service (Production-ready, part 3)

Workflow preview

Workflow preview
100%
AI chatbot call center: Taxi service (Production-ready, part 3) preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

Workflow Name: ️ Taxi Service 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 AI...

Best for

  • Support Chatbot automation workflows
  • AI Chatbot automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.executeworkflowtrigger, n8n-nodes-base.set, @n8n/n8n-nodes-langchain.chattrigger, @n8n/n8n-nodes-langchain.agent, @n8n/n8n-nodes-langchain.memorypostgreschat, n8n-nodes-base.redistool, @n8n/n8n-nodes-langchain.lmchatxaigrok, n8n-nodes-base.postgrestool

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by ChatPayLabs.

Original n8n.io source

1.1 Workflow description

Title
AI chatbot call center: Taxi service (Production-ready, part 3)
Workflow name
AI chatbot call center: Taxi service (Production-ready, part 3)

Workflow Name: 🛎️ Taxi Service

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
  • AI Agent node
  • If node, Switch node, Code node, Edit Fields (Set)

Prerequisite

  • Execute Sub-workflow Trigger: Taxi Service Workflow (or your own node)
  • Sub-workflow: Taxi Service Provider (or your own node)
  • Sub-workflow: Demo Call Back (or your own node)

Production Features

  • Scaling Design for n8n Queue mode in production environment
  • Service Data from external Database with Caching Mechanism
  • Optional Long Terms Memory design
  • Find Route Distance using Google Map API
  • Optional Multi-Language Wait Output example
  • Error Management

What this workflow does?

This is a n8n Taxi Service Workflow demo. It is the core node for Taxi Service. It will receive message from the Call Center Workflow, handling the QA from the caller, and pass to each of the Taxi Service Provider Workflow to process the estimation.

How it works

  • The Flow Trigger node will wait for the message from Call Center or other Sub-workflow.
  • When message is received, it will first check for the matching Service from the PostgreSQL database.
  • If no service or service is inactive, output Error.
  • Next, always reset the Session Data in Cache, with channel_no set to taxi
  • Next, delete the previous Route Data in Cache
  • Trigger a AI Agent to process the fare estimation question to create the Route Data
  • Use the Google Map Route API to calculate the distance.
  • Repeat until created the route data, then pass to all the Taxi Service Provider for an estimation.

Set up instructions

  1. Pull and Set up the required SQL from our Github repository.
  2. Create you Redis credentials, refer to n8n integration documentation for more information.
  3. Select your Credentials in Service Cache, Save Service Cache, Reset Session, Delete Route Data, Route Data, Update User Session and Create Route Data.
  4. Create you Postgres credentials, refer to n8n integration documentation for more information.
  5. Select your Credentials in Load Service Data, Postgres Chat Memory, Load User Memory and Save User Memory.
  6. Modify the AI Agent prompt to fit your need
  7. Set you Google Map API key in Find Route Distance

How to adjust it to your needs

  1. By default, this template will use the sys_service table provider information, you could change it for your own design.
  2. You can use any AI Model for the AI Agent node
  3. Learn we use the prompt for the Load/Save User Memory on demand.
  4. Include is our prompt for the taxi service. It is a flexible design which use the data from the Service node to customize the prompt, so you could duplicate this workflow as another service.
  5. Create difference Taxi Providers to process the and feedback the estimate.

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Flow Trigger

Type / Role
n8n-nodes-base.executeWorkflowTrigger - executeWorkflowTrigger
Config choices
Version 1.1

Block 2 - Input

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 3 - Test Trigger

Type / Role
@n8n/n8n-nodes-langchain.chatTrigger - chatTrigger
Config choices
Version 1.1

Block 4 - Test Fields

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 5 - AI Agent

Type / Role
@n8n/n8n-nodes-langchain.agent - agent
Config choices
Version 1.9

Block 6 - Postgres Chat Memory

Type / Role
@n8n/n8n-nodes-langchain.memoryPostgresChat - memoryPostgresChat
Config choices
Version 1.3

Block 7 - Output

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 8 - Update User Session

Type / Role
n8n-nodes-base.redisTool - redisTool
Config choices
Version 1

Block 9 - xAI @grok-2-1212

Type / Role
@n8n/n8n-nodes-langchain.lmChatXAiGrok - lmChatXAiGrok
Config choices
Version 1

Block 10 - Load User Memory

Type / Role
n8n-nodes-base.postgresTool - postgresTool
Config choices
Version 2.6

Block 11 - Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 12 - If Service Cache

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Block 13 - Service Cache

Type / Role
n8n-nodes-base.redis - redis
Config choices
Version 1

Block 14 - Load Service Data

Type / Role
n8n-nodes-base.postgres - postgres
Config choices
Version 2.6

Block 15 - Save Service Cache

Type / Role
n8n-nodes-base.redis - redis
Config choices
Version 1

Block 16 - If Active

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Block 17 - Inactive Output

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 18 - Service

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 19 - Sticky Note3

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 20 - Error Output

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 21 - Sticky Note1

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 22 - Save User Memory

Type / Role
n8n-nodes-base.postgresTool - postgresTool
Config choices
Version 2.6

Block 23 - Create Route Data

Type / Role
n8n-nodes-base.redisTool - redisTool
Config choices
Version 1

Block 24 - Delete Route Data

Type / Role
n8n-nodes-base.redis - redis
Config choices
Version 1

Showing the first 24 of 40 workflow blocks. Download the JSON for the full node graph.

3. Summary Table

Workflow AI chatbot call center: Taxi service (Production-ready, part 3)
Complexity advanced
Nodes 40
Categories Support Chatbot, AI Chatbot
Author ChatPayLabs
Published 14 May 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/4046/4046.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does AI chatbot call center: Taxi service (Production-ready, part 3) do?

Workflow Name: ️ Taxi Service 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 AI...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Support Chatbot, AI Chatbot use case.