Skip to main content

Taxi service provider (production-ready, part 4)

Workflow preview

Workflow preview
100%
Taxi service provider (production-ready, part 4) 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 Provider 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...

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-nodes-base.code, @n8n/n8n-nodes-langchain.lmchatxaigrok, n8n-nodes-base.postgrestool, n8n-nodes-base.stickynote

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
Taxi service provider (production-ready, part 4)
Workflow name
Taxi service provider (production-ready, part 4)

Workflow Name: πŸ€– Taxi Service Provider

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

Prerequisite

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

Production Features

  • Scaling Design for n8n Queue mode in production environment
  • Provider Data from external Database with Caching Mechanism
  • Optional Score design output
  • Optimize Taxi Provider Prompt from database
  • Error Management

What this workflow does?

This is a n8n Taxi Provider Workflow demo. It will receive message from the Taxi Service Workflow, process the estimation and return to the caller.

How it works

  • The Flow Trigger node will wait for the message from other Sub-workflow.
  • When message is received, it will first check for the matching Provider from the PostgreSQL database.
  • Then it will increase a Provider Number in Redis for selection later
  • Trigger a AI Agent to process the fare estimation and create a NEW booking
  • Finally, send the AI response to the Call Output
  • Note: if the Provider is set to inactive, it will do nothing

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 Provider Cache, Save Provider Cache and Provider Number.
  4. Create you Postgres credentials, refer to n8n integration documentation for more information.
  5. Select your Credentials in Load Provider Data and Create Booking Data.
  6. Modify the AI Agent prompt to fit your need

How to adjust it to your needs

  1. By default, this template will use the sys_provider table provider information, you could change it for your own design.
  2. You can use any AI Model for the AI Agent node
  3. Include is our prompt for the taxi service provider. It is a flexible design which use the data from the Provider Cache to customize the prompt, so you could create more Taxi Service Providers by duplicate this workflow in the Taxi Service node.

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 - Code

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 7 - xAI @grok-2-1212

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

Block 8 - Create Booking Data

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

Block 9 - Sticky Note3

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

Block 10 - Provider Number

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

Block 11 - Calculator

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

Block 12 - Sticky Note

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

Block 13 - If Active

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

Block 14 - Provider Cache

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

Block 15 - Load Provider Data

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

Block 16 - Save Provider Cache

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

Block 17 - Parse Provider

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 18 - Provider

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

Block 19 - Sticky Note1

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

Block 20 - Error Output1

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

Block 21 - If Score

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

Block 22 - Output w/ Score

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

Block 23 - Output w/o Score

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

Block 24 - Sticky Note4

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

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

3. Summary Table

Workflow Taxi service provider (production-ready, part 4)
Complexity advanced
Nodes 30
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/4047/4047.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 Taxi service provider (production-ready, part 4) do?

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

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.