Block 1 - Telegram Trigger
- Type / Role
- n8n-nodes-base.telegramTrigger - telegramTrigger
- Config choices
- Version 1
This workflow is provided as-is. Please review and test before using in production.
How it works This workflow automatically transcribes and translates voice messages from Telegram to Slack , enabling seamless communication between Japanese and English speakers. In our real wor...
n8n-nodes-base.telegramtrigger, n8n-nodes-base.if, n8n-nodes-base.set, n8n-nodes-base.httprequest, n8n-nodes-base.function, n8n-nodes-base.code, @n8n/n8n-nodes-langchain.openai, n8n-nodes-base.stickynote
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Tomohiro Goto.
Original n8n.io sourceThis workflow automatically transcribes and translates voice messages from Telegram to Slack, enabling seamless communication between Japanese and English speakers.
In our real-world use case, our distributed team often sends short voice updates on Telegram — but most discussion happens on Slack.
Before this workflow, we constantly asked:
This workflow fixes that problem without changing anyone’s communication habits.
Built with n8n, OpenAI Whisper, and GPT-4o-mini, it automatically:
TELEGRAM_BOT_TOKEN OPENAI_API_KEY_HEADER SLACK_BOT_TOKEN_HEADERchat:write, files:write, channels:history OpenAI Whisper × GPT-4o-mini × n8n × Telegram Bot API × Slack API
A complete multilingual voice-to-text bridge — connecting speech, translation, and collaboration across platforms. 🌍
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.
| Workflow | Voice translator bridge (Telegram → Slack) with GPT-4o-mini + Whisper |
|---|---|
| Complexity | advanced |
| Nodes | 24 |
| Categories | Personal Productivity, Multimodal AI |
| Author | Tomohiro Goto |
| Published | 26 Oct 2025 |
Use the JSON export at /data/workflows/10187/10187.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
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.
How it works This workflow automatically transcribes and translates voice messages from Telegram to Slack , enabling seamless communication between Japanese and English speakers. In our real wor...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
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 Personal Productivity, Multimodal AI use case.