Main Function to Receive and Send Telegram Messages
Configured with Agent, Google Tasks Tool, OpenAI Chat Model, Mcp Client Tool, and additional nodes. Review the connections and setup before adapting this template.
Node categories in this workflow
- Trigger
- AI & models
- Integration
- Data store
- Transform
- Messaging
- Routing
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 |
|---|---|---|---|
| Incoming Message | Trigger | Telegram Trigger | See node parameters |
| MCP Server Trigger | Trigger | Mcp Trigger | See node parameters |
| AI Agent | AI & models | Agent | See node parameters |
| MCP Client | Integration | Mcp Client Tool | See node parameters |
| OpenAI Chat Model | AI & models | OpenAI Chat Model | See node parameters |
| Simple Memory | Data store | Memory Buffer Window | See node parameters |
| chatInput | Transform | Edit Fields | See node parameters |
| create_todays_task | Integration | Google Tasks Tool | See node parameters |
| chatOutput | Transform | Edit Fields | See node parameters |
| sendMessage | Messaging | Telegram | See node parameters |
| create_upcoming_task | Integration | Google Tasks Tool | See node parameters |
| complete_task | Integration | Google Tasks Tool | update |
| get_todays_tasks | Integration | Google Tasks Tool | getAll |
| get_upcoming_tasks | Integration | Google Tasks Tool | getAll |
| Switch | Routing | Switch | See node parameters |
| audio_id | Transform | Edit Fields | See node parameters |
| download_audio | Messaging | Telegram | file |
| transcribeAudio | AI & models | Open Ai | audio / transcribe |
| audioInput | Transform | Edit Fields | See node parameters |
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
googleTasksOAuth2ApiopenAiApitelegramApi
Workflow notes
Main Function to Receive and Send Telegram Messages
Main Function to Receive and Send Telegram Messages
Purpose and structure
This folder contains the Main Function to Receive and Send Telegram Messages workflow. Its executable nodes use agent, googleTasksTool, lmChatOpenAi, mcpClientTool, mcpTrigger, memoryBufferWindow, openAi, set, switch, telegram, telegramTrigger. 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
Incoming Message, MCP Server Trigger
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/Telegram/0882_Telegram_Googletaskstool_Create_Triggered.json MIT; preserve source notices.
Canvas section labels
These name areas of the original canvas; they do not include explanatory instructions.
- Main Function to Receive and Send Telegram Messages
- MCP Server to Carry Out Actions