HumationHuman + Automation
Back to Catalog

AI chatbot call center: demo call back (production-ready, part 6)

ChatPayLabsChatPayLabs
442 views
2/3/2026
DiscordWeatherAutomationHTTP RequestOpenWeatherMap
Official Page

Workflow Name: 💬 Demo Call Back

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
  • Telegram node
  • HTTP Request node
  • If node, Code node, Edit Fields (Set)

Prerequisite

  • Execute Sub-workflow Trigger: your own node
  • MiniMax Account (https://www.minimax.io/)

Production Features

  • Scaling Design for n8n Queue mode in production environment
  • Optional Provider Data from external Database with Caching Mechanism.
  • Optional AI Clone Voice Message response via MiniMax API with Multi-Languages support.
  • Optional Backup Chat Log to Database, so you can use in APP/API building.
  • Testing Flow with or without dependance on other workflow.
  • Multi Chatbot (This is a demo for Telegram, you can add WhatsApp, Line, etc)
  • Error Management

What this workflow does?

This is a n8n Telegram Output Workflow. It will receive message from other Sub-workflow then output to Telegram for Message, or Replay Message and extra Voice Message.

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 determine if it is a Voice message to Text message.
  • OPTIONAL. For voice message, use the MiniMax API to generate a voice message, then send it to Telegram.
  • Finally, send the text to Telegram.

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 and Save Provider Cache.
  4. Create you Postgres credentials, refer to n8n integration documentation for more information.
  5. Select your Credentials in Load Member Data, Create Chat Log Input, and Create Chat Log Output.
  6. Create you Telegram credentials, refer to n8n integration documentation for more information.
  7. Select your Credentials in Telegram Voice Output, Telegram Reply Output, and Telegram Output.

AI Clone Voice setup instructions (Optional)

You can clone any voice with MiniMax

  1. Go to https://www.minimax.io/ and create a MiniMax account
  2. Setup the Database with the required variables found in the MiniMax TTS node
  3. That’s it

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. The demo use MiniMax API for AI voice cloning, you could implement any other AI your choice.
  3. The Backup Chat Log will backup all chat conversion line by line. You can use it for you own APP/API development.

AI Chatbot Call Center Demo - Production Ready Part 6

This n8n workflow serves as a foundational component for an AI Chatbot Call Center demo, specifically focusing on the backend logic for handling chat messages and interacting with various data stores. It processes incoming chat messages, determines their intent, and then performs actions such as querying databases or making API calls, ultimately preparing a response.

What it does

  1. Listens for Chat Messages: The workflow is triggered by incoming chat messages, likely from a conversational AI platform or a custom chat interface.
  2. Initial Data Transformation: It processes the incoming chat message data, potentially extracting key information or reformatting it for subsequent steps.
  3. Conditional Logic (Switch): It uses a Switch node to route the workflow based on the content or intent of the chat message.
  4. Database Interaction (Postgres & Redis): Depending on the determined intent, the workflow interacts with either a PostgreSQL or Redis database to retrieve or store information.
  5. External API Calls: It can make HTTP requests to external APIs, likely for fetching additional data or triggering other services.
  6. Response Preparation: It prepares a response based on the actions performed, which could involve data retrieved from databases or API calls.
  7. Sends Telegram Messages: In some branches, it sends messages via Telegram, potentially for notifications or human-in-the-loop interventions.
  8. Workflow Execution Trigger: It can also be triggered by another workflow, indicating it might be a sub-workflow in a larger automation.

Prerequisites/Requirements

  • n8n Instance: A running instance of n8n.
  • PostgreSQL Database: Access to a PostgreSQL database with appropriate credentials.
  • Redis Instance: Access to a Redis instance with appropriate credentials.
  • Telegram Bot Token: A Telegram bot token and chat ID if the Telegram node is to be used for notifications.
  • External API Endpoints: Any necessary API keys or endpoints for HTTP Request nodes.

Setup/Usage

  1. Import the Workflow: Import the provided JSON into your n8n instance.
  2. Configure Credentials:
    • Set up Postgres credentials (Host, Port, Database, User, Password).
    • Set up Redis credentials (Host, Port, Password).
    • Configure Telegram credentials (Bot Token, Chat ID) if you intend to use the Telegram notification feature.
  3. Configure Nodes:
    • Chat Trigger: Ensure the "When chat message received" node is configured to listen to the correct chat platform or webhook.
    • Edit Fields (Set): Review and adjust the data transformation logic in the "Edit Fields" node as needed for your specific data structure.
    • Switch: Customize the conditions in the "Switch" node to accurately route messages based on your AI's intent detection or message content.
    • Postgres / Redis: Adjust the operations (e.g., SELECT, INSERT, GET, SET) and queries in the database nodes to match your database schema and requirements.
    • HTTP Request: Configure the URLs, headers, and body for any external API calls.
    • Code: If the "Code" node is used, ensure the JavaScript logic aligns with your data processing needs.
  4. Activate the Workflow: Once configured, activate the workflow to start processing incoming chat messages.

Related Templates

Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets

This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.

Ranjan DailataBy Ranjan Dailata
161

Two-way property repair management system with Google Sheets & Drive

This workflow automates the repair request process between tenants and building managers, keeping all updates organized in a single spreadsheet. It is composed of two coordinated workflows, as two separate triggers are required — one for new repair submissions and another for repair updates. A Unique Unit ID that corresponds to individual units is attributed to each request, and timestamps are used to coordinate repair updates with specific requests. General use cases include: Property managers who manage multiple buildings or units. Building owners looking to centralize tenant repair communication. Automation builders who want to learn multi-trigger workflow design in n8n. --- ⚙️ How It Works Workflow 1 – New Repair Requests Behind the Scenes: A tenant fills out a Google Form (“Repair Request Form”), which automatically adds a new row to a linked Google Sheet. Steps: Trigger: Google Sheets rowAdded – runs when a new form entry appears. Extract & Format: Collects all relevant form data (address, unit, urgency, contacts). Generate Unit ID: Creates a standardized identifier (e.g., BUILDING-UNIT) for tracking. Email Notification: Sends the building manager a formatted email summarizing the repair details and including a link to a Repair Update Form (which activates Workflow 2). --- Workflow 2 – Repair Updates Behind the Scenes:\ Triggered when the building manager submits a follow-up form (“Repair Update Form”). Steps: Lookup by UUID: Uses the Unit ID from Workflow 1 to find the existing row in the Google Sheet. Conditional Logic: If photos are uploaded: Saves each image to a Google Drive folder, renames files consistently, and adds URLs to the sheet. If no photos: Skips the upload step and processes textual updates only. Merge & Update: Combines new data with existing repair info in the same spreadsheet row — enabling a full repair history in one place. --- 🧩 Requirements Google Account (for Forms, Sheets, and Drive) Gmail/email node connected for sending notifications n8n credentials configured for Google API access --- ⚡ Setup Instructions (see more detail in workflow) Import both workflows into n8n, then copy one into a second workflow. Change manual trigger in workflow 2 to a n8n Form node. Connect Google credentials to all nodes. Update spreadsheet and folder IDs in the corresponding nodes. Customize email text, sender name, and form links for your organization. Test each workflow with a sample repair request and a repair update submission. --- 🛠️ Customization Ideas Add Slack or Telegram notifications for urgent repairs. Auto-create folders per building or unit for photo uploads. Generate monthly repair summaries using Google Sheets triggers. Add an AI node to create summaries/extract relevant repair data from repair request that include long submissions.

Matt@VeraisonLabsBy Matt@VeraisonLabs
208

Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax

Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions

Daniel NkenchoBy Daniel Nkencho
601