receive telegram events and fetch voice message and translate audio open ai
Configured with Agent, Extract From File, HTTP Request, OpenAI Chat Model, and additional nodes. Review the connections and setup before adapting this template.
Node categories in this workflow
- Trigger
- Routing
- Messaging
- AI & models
- Transform
- Integration
- Web / API
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| Receive Telegram Messages | Trigger | Telegram Trigger | See node parameters |
| Voice or Text? | Routing | Switch | See node parameters |
| Fetch Voice Message | Messaging | Telegram | file |
| Transcribe Voice to Text | AI & models | Open Ai | audio / translate |
| Prepare for LLM | Transform | Edit Fields | See node parameters |
| AI Agent | AI & models | Agent | See node parameters |
| OpenAI Chat Model | AI & models | OpenAI Chat Model | See node parameters |
| SerpAPI | Integration | Tool Serp Api | See node parameters |
| Structured Output Parser | Transform | Output Parser Structured | See node parameters |
| Extract from File | Transform | Extract From File | binaryToPropery |
| Prepare Final Output | Transform | Edit Fields | See node parameters |
| Generate Image | Web / API | HTTP Request | POST |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
httpHeaderAuthhuggingFaceApiopenAiApiserpApitelegramApi
Workflow notes
Sticky Note2
This workflow listens for incoming voice or text messages from Telegram users.
Sticky Note3
Voice messages are fetched from Telegram and transcribed into text using OpenAI's Whisper API.
Sticky Note
The AI agent uses the OpenAI Chat Model and SerpAPI tool to conduct research and generate social media content and an image prompt based on the user request.
Sticky Note1
An image is generated using the image prompt
receive telegram events and fetch voice message and translate audio open ai
receive telegram events and fetch voice message and translate audio open ai
Purpose and structure
This folder contains the receive telegram events and fetch voice message and translate audio open ai workflow. Its executable nodes use agent, extractFromFile, httpRequest, lmChatOpenAi, openAi, outputParserStructured, set, switch, telegram, telegramTrigger, toolSerpApi. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
Receive Telegram Messages
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Http/0771_HTTP_Telegram_Create_Webhook.json MIT; preserve source notices.