Tags
n8nPRO
Workflow Name: 🤙 Telegram Call In
Template was created in n8n v1.90.2
Skill Level: High
Categories: n8n, Chatbot
Stacks
- Chat Trigger node
- Telegram Trigger node
- Redis node
- Postgres node
- Execute Sub-workflow
- If node, Code node, Edit Fields (Set), Extract From File
Prerequisite
- Community nodes: n8n-nodes-google-speech
- Sub-workflow: Demo Call Back
- Sub-workflow: Demo Call Center
Production Features
- Optional Member Data from external Database with Caching Mechanism.
- Optional Voice Message to Text Message via Google STT API with Multi-Languages support.
- Testing Flow with or without dependance on other workflow.
- Error Management
What this workflow does?
This is a n8n Telegram Call In Workflow. It will wait for message from Telegram bot and sent to the Call Center to process.
How it works
- The Telegram Trigger node will wait for the message from the Telegram bot.
- When message is received, it will first check for the matching Member from the PostgreSQL database.
- Then determine if it is a Text message or Voice message.
- For voice message, use the Google Speech to Text API to transcript it into text.
- Finally, pass the text to the next flow, i.e. the Call Center.
Set up instructions
- Pull and Set up the required SQL from our Github repository.
- Go User > Settings > Community nodes, install n8n-nodes-google-speech node
- Follow https://www.npmjs.com/package/n8n-nodes-google-speech
- Setup the Google STT node
- Create you Telegram credentials, refer to n8n integration documentation for more information.
- Select your Credentials in Telegram Trigger
- Create you Redis credentials, refer to n8n integration documentation for more information.
- Select your Credentials in Member Cache and Save Member Cache.
- Create you Postgres credentials, refer to n8n integration documentation for more information.
- Select your Credentials in Load Member Data.
- FOR TEST ONLY. Enable the Telegram Test Output for testing from the Test Input.
How to adjust it to your needs
- By default, this template will use the sys_member table for member information, you could change it for your own design.
- The demo implementation does not include failed member loading situation, you should implement based on your needs, e.g. if is_active is not true, do…
- You can replace the sub-workflow Demo Call Back and Demo Call Center to another flow as needs.
Support Us 🦄
We're an indie AI chatbot startup in Hong Kong, seeking your support to fuel our project. In return, we are sharing our core infrastructure for your reference to speed up your project. Welcome to the world of AI 😘
Buy the Full AI Chatbot Call Center Package for US$500 👉 Here
Download Part 1a For US$80 👉 Here
Resources
https://github.com/ChatPayLabs/n8n-chatbot-core