telegram and list noco db and receive telegram events
Configured with Function, HTTP Request, Noco Db, Switch, and additional nodes. Review the connections and setup before adapting this template.
Node categories in this workflow
- Code
- Transform
- Routing
- Messaging
- Data store
- Trigger
- 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 |
|---|---|---|---|
| chatID | Code | Function | See node parameters |
| Merge | Transform | Merge | See node parameters |
| Switch | Routing | Switch | See node parameters |
| IF | Routing | If | See node parameters |
| msg_greet | Messaging | Telegram | See node parameters |
| msg_welcomeback | Messaging | Telegram | See node parameters |
| msg_help | Messaging | Telegram | See node parameters |
| msg_wrongcommand | Messaging | Telegram | See node parameters |
| New user? | Code | Function | See node parameters |
| CheckUser | Data store | Noco Db | getAll |
| LoadDictionary | Data store | Noco Db | getAll |
| botmessages | Code | Function | See node parameters |
| Telegram Trigger | Trigger | Telegram Trigger | See node parameters |
| HTTP AddUser | Web / API | HTTP Request | See node parameters |
| HTTP UpdateUser | Web / API | HTTP Request | See node parameters |
| AddUser | Data store | Noco Db | create |
| UpdateUser | Data store | Noco Db | update |
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
httpHeaderAuthnocoDbtelegramApi
Workflow notes
chatID
username and language
Merge
Wait for dictionary to load
Switch
check bot commands
What's this?
What's this?
Due to some breaking API changes in NocoDB some of its node options are not working at the moment (MAY 2022). These two nodes were replaced by HTTP request nodes. Functionality is still the same.
telegram and list noco db and receive telegram events
telegram and list noco db and receive telegram events
Purpose and structure
This folder contains the telegram and list noco db and receive telegram events workflow. Its executable nodes use function, httpRequest, if, merge, nocoDb, 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
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/Nocodb/0193_Nocodb_Telegram_Create_Webhook.json MIT; preserve source notices.