agent and receive telegram events and google sheets
Configured with Agent, Aggregate, Google Sheets, OpenAI Chat Model, and additional nodes. Review the connections and setup before adapting this template.
Node categories in this workflow
- AI & models
- Data store
- Trigger
- Transform
- Messaging
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 |
|---|---|---|---|
| AI Agent | AI & models | Agent | See node parameters |
| OpenAI Chat Model | AI & models | OpenAI Chat Model | See node parameters |
| Simple Memory | Data store | Memory Buffer Window | See node parameters |
| Telegram Trigger | Trigger | Telegram Trigger | See node parameters |
| Retrive Vocabulary | Data store | Google Sheets | See node parameters |
| Aggregate Vocabulary Lists | Transform | Aggregate | See node parameters |
| Answer to the User | Messaging | Telegram | 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
None declared. HTTP requests and Code nodes may still need configuration.
Workflow notes
3. Do you need more details?
3. Do you need more details?
Find a step-by-step guide in this tutorial 🎥 Watch My Tutorial
AI Agent
Pinyin + Example
1. Workflow Trigger with Telegram Message
1. Workflow Trigger with Telegram Message
- The workflow is triggered by a user message.
- The second node retrieves the vocabulary list from a Google Sheet.
- The third node combines all the words in Chinese and English in two distinctive lists.
How to setup?
- Telegram Node: set up your telegram bot credentials Learn more about the Telegram Trigger Node
- Retrieve Vocabulary from a Google Sheet Node:
- Add your Google Sheet API credentials to access the Google Sheet file
- Select the file using the list, an URL or an ID
- Select the sheet in which you have stored your vocabulary list Learn more about the Google Sheet Node
2. Conversational AI Agent
2. Conversational AI Agent
The AI agent will take as inputs the two vocabulary lists and user's message to asks questions and process answers. Conversations are recorded by chat id; each user has its own conversation with the bot.
How to setup?
- Telegram Nodes: set up your telegram bot credentials Learn more about the Telegram Trigger Node
- AI Agent with the Chat Model:
- Add a chat model with the required credentials (Example: Open AI 4o-mini)
- Adapt the system prompt with the target learning language and the format of the question you want to have.
agent and receive telegram events and google sheets
agent and receive telegram events and google sheets
Purpose and structure
This folder contains the agent and receive telegram events and google sheets workflow. Its executable nodes use agent, aggregate, googleSheets, lmChatOpenAi, memoryBufferWindow, 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
Telegram 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/Aggregate/0800_Aggregate_Telegram_Automate_Triggered.json MIT; preserve source notices.