Skip to main content

AI chatbot call center: Demo call center (production-ready, part 2)

Workflow preview

Workflow preview
100%
AI chatbot call center: Demo call center (production-ready, part 2) 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: ️ Demo Call Center 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...

Best for

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

Tools used

n8n-nodes-base.redis, n8n-nodes-base.set, @n8n/n8n-nodes-langchain.chattrigger, n8n-nodes-base.executeworkflowtrigger, n8n-nodes-base.if, n8n-nodes-base.stickynote, n8n-nodes-base.switch, @n8n/n8n-nodes-langchain.agent

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: Demo call center (production-ready, part 2)
Workflow name
AI chatbot call center: Demo call center (production-ready, part 2)

Workflow Name: ☎️ Demo Call Center

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: Telegram Call In Workflow (or your own node)
  • Sub-workflow: Taxi Service (or your own node)
  • Sub-workflow: Taxi Booking Worker (or your own node)
  • Sub-workflow: Demo Call Back (or your own node)

Production Features

  • Scaling Design for n8n Queue mode in production environment
  • Optional Rate Limit design to prevent overused
  • Optional Long Terms Memory design
  • Multi-Service design
  • Testing Flow with or without dependance on other workflow.
  • Error Management

What this workflow does?

This is a n8n Demo Call Center Workflow demo. It is the main entry node for a Multiple Services Chatbot. It will receive message from the Call In Workflow, and decide which service should be use, or which service provider should be process the selected result.

How it works

  • The Flow Trigger node will wait for the message from the Call In Workflow or other Sub-workflow.
  • When message is received, it will first check for the Rate Limit.
  • If ok, load the Session Data from Cache.
  • Next, check the current Session for the channel_no (default is chat).
  • if channel_no is chat, continue to the AI Agent for chit-chat.
  • if channel_no is taxi or others, pass to the Service Input (i.e. Taxi Service) or Service Worker (i.e. Taxi Booking Worker) to handle it directly.
  • The AI Agent should decide which service (i.e. taxi) will be used at some point and update the channel_no in Session, and pass to the Service Node (i.e. Taxi Service) at once.
  • In case of any error, reply the error in Call Back.

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 Rate Limit, Session, Provider and New Session.
  4. Create you Postgres credentials, refer to n8n integration documentation for more information.
  5. Select your Credentials in Postgres Chat Memory, Load User Memory and Save User Memory.
  6. Modify the AI Agent prompt to fit your need

How to adjust it to your needs

  1. In Session, we have a timestamp fields which is created at the Input node. The usage of this is combined to use with the session id to create a unique session, since some media, such as Telegram, do not have a unique session along with the chat.
  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. You can add more service similar to this.

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

Type / Role
n8n-nodes-base.redis - redis
Config choices
Version 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 - Flow Trigger

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

Block 6 - Rate Limit

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

Block 7 - If Rated

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

Block 8 - Rated Output

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

Block 9 - Chat Memory

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

Block 10 - Sticky Note3

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

Block 11 - Sticky Note

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

Block 12 - Sticky Note1

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

Block 13 - Sticky Note2

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

Block 14 - Sticky Note4

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

Block 15 - Channel Switch

Type / Role
n8n-nodes-base.switch - switch
Config choices
Version 3.2

Block 16 - Sticky Note5

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

Block 17 - AI Agent

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

Block 18 - xAI @grok-2-1212

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

Block 19 - Postgres Chat Memory

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

Block 20 - Load User Memory

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

Block 21 - Save User Memory

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

Block 22 - Sticky Note6

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

Block 23 - Taxi Service

Type / Role
@n8n/n8n-nodes-langchain.toolWorkflow - toolWorkflow
Config choices
Version 2.2

Block 24 - Provider

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

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

3. Summary Table

Workflow AI chatbot call center: Demo call center (production-ready, part 2)
Complexity advanced
Nodes 38
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/4045/4045.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: Demo call center (production-ready, part 2) do?

Workflow Name: ️ Demo Call Center 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...

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.