Telegram Call-In AI Chatbot for Call Centers (Prod-Ready Pt1)

Production-ready n8n workflow that processes Telegram messages/voice notes, transcribes voice to text via Google STT (multi-lang), checks users in Postgres with Redis cache, and forwards to call center.

n8n
Telegram Call-In AI Chatbot for Call Centers (Prod-Ready Pt1)

This workflow automates Telegram call-in handling for AI chatbots in call centers. It triggers on incoming Telegram messages via the Telegram Trigger node, checks for matching user data in a PostgreSQL database (with optional Redis caching for performance), and differentiates between text and voice messages. Voice notes are transcribed to text using the Google Speech-to-Text API (n8n-nodes-google-speech community node) with multi-language support.

Key production features include scaling design for n8n Queue mode, robust error management, and flexibility to test without dependencies. It integrates Redis for caching member data, Postgres for storage, and Execute Sub-workflow nodes to pass processed text to downstream flows like 'Demo Call Center' or 'Demo Call Back'.

Benefits: Saves hours of manual transcription and routing, enables 24/7 automated call centers, reduces latency with caching, and scales seamlessly. Ideal use cases: Customer support bots, appointment booking via voice/text, sales inquiries, or any Telegram-based service needing AI processing. High skill level; requires setup of community nodes and SQL schema from GitHub.

$24.99
Last updated October 17, 2026
30-day money-back guarantee
Instant download
Lifetime updates included

New buyers can create an account from the cart to unlock a controlled $10 first-purchase credit on eligible orders of $25+.

Secure checkout powered by Stripe

Support

How to import this workflow into n8n

  1. 1Purchase or download the workflow to get the n8n workflow JSON file.
  2. 2In your n8n instance, open Workflows and choose "Import from File" (or paste the JSON with Ctrl+V on the canvas).
  3. 3Open each node marked with a credential warning and connect your own accounts and API keys.
  4. 4Run the workflow once manually to verify the data flow, then toggle it to Active.

Related Productivity workflows

More from Bruno Jonsson

Need this deployed? We'll set it up for you.

Our automation experts deploy this workflow in your stack, connect your accounts, and verify it works — or build a custom solution from scratch.