OpenRuna
Sign in
← Workflows

0864_Telegram_Splitout_Create_Triggered

23 nodes · chat, lmChatOpenAi, outputParserStructured, telegram, openAi, limit

Engine
n8n
Nodes
23
Trigger
scheduled/triggered
Source file
0864_Telegram_Splitout_Create_Triggered.json

Workflow flow

IntegrationsChatLmChatOpenAiOutputParserStructuredTelegramOpenAILimitAgentSplit OutGoogle Sheets@n8n/n8n-nodes-langchain.chat@n8n/n8n-nodes-langchain.lmChatOpenAi@n8n/n8n-nodes-langchain.outputParserStructured+5 more
100%
TRIGGER

When chat message received

@n8n/n8n-nodes-langchain.chat

OpenAI Chat Model

@n8n/n8n-nodes-langchain.lmChatOpenAi

Structured Output Parser

@n8n/n8n-nodes-langchain.outputParserStructured

TRIGGER

Receive Telegram message

Telegram

If it's a voice message

IF

Get Audio File

Telegram

Set chatInput from message

Set

Transcribe Recording

@n8n/n8n-nodes-langchain.openAi

Set chatInput from voice

Set

List of Ingredients and nutrients

@n8n/n8n-nodes-langchain.agent

Explode the list

Split Out

Add date

Code

Store in sheet

Google Sheets

Limit

Limit

Respond message

Telegram

15 steps · flows top to bottom, branches left to right

Browse by integration

Browse all integrations →

Import into n8n

  1. Download the n8n JSON file (full or sanitized).
  2. In n8n: Workflows → Import from file.
  3. Open each node and reconnect credentials to your accounts.
  4. Test with manual execution before enabling triggers.

Sanitized JSON removes credential IDs — safer for sharing. Flow graph JSON is OpenRuna's lightweight format for diagrams and other tools, not n8n import.

View source corpus ↗

Overview

0864_Telegram_Splitout_Create_Triggered (23-node n8n automation, chat, lmChatOpenAi, outputParserStructured, telegram, openAi, limit, agent, splitOut) is free on OpenRuna — view the graph and export the JSON to import into n8n.

What this workflow does

This n8n workflow, "0864_Telegram_Splitout_Create_Triggered", wires together chat, lmChatOpenAi, outputParserStructured, telegram, openAi, limit, agent, splitOut in 23 nodes. 23 nodes · chat, lmChatOpenAi, outputParserStructured, telegram, openAi, limit A scheduled/triggered entry point kicks it off, and each node passes data to the next until the run completes. OpenRuna shows the full flow diagram, an integration breakdown, and a one-click JSON export for n8n's "Import from file". Use it to learn integration patterns, fork it for your own use case, or deploy it quickly after reconnecting credentials.

Use cases

  • Import "0864_Telegram_Splitout_Create_Triggered" into n8n, reconnect credentials for chat, lmChatOpenAi, outputParserStructured, telegram, openAi, limit, agent, splitOut, and run the same automation in your own workspace.
  • Use it as a starting template when wiring chat, lmChatOpenAi, outputParserStructured, telegram, openAi, limit, agent, splitOut — adjust node parameters to your accounts and record IDs.
  • Study how data moves from chat to lmChatOpenAi before building your own variant.
  • Share it with your team as a documented reference for scheduled/triggered automations in the chat stack.

Example output

Imported into n8n, "0864_Telegram_Splitout_Create_Triggered" exposes 23 configured nodes. Trigger type: scheduled/triggered. Integrations: chat, lmChatOpenAi, outputParserStructured, telegram, openAi, limit, agent, splitOut. Open each node after import to map credentials to your own chat and lmChatOpenAi accounts. Run it once in test mode to verify any branch logic (Switch/IF nodes) before enabling production triggers.

Tips by platform

Claude

Ask Claude to turn the "0864_Telegram_Splitout_Create_Triggered" JSON into a plain-English runbook, node by node. It can flag where chat rate limits or missing retries might bite before you go live.

ChatGPT

Drop the workflow JSON or this OpenRuna page URL into ChatGPT and ask for a step-by-step runbook: triggers, branches, and which fields to customise for chat, lmChatOpenAi, outputParserStructured, telegram, openAi, limit, agent, splitOut. Handy for onboarding teammates new to n8n.

Cursor

In Cursor, ask Agent mode to parameterise "0864_Telegram_Splitout_Create_Triggered" — extract chat IDs and secrets into environment variables without changing the 23-node structure.

Frequently asked questions

How do I import "0864_Telegram_Splitout_Create_Triggered" into n8n?
Click Download n8n JSON on this page, then in n8n choose Workflows → Import from file and select the downloaded file. Reconnect credentials on each node — the export carries credential IDs from the original author's instance, not working secrets.
Which integrations does "0864_Telegram_Splitout_Create_Triggered" use?
It uses: chat, lmChatOpenAi, outputParserStructured, telegram, openAi, limit, agent, splitOut. The flow diagram above shows how each service connects across the 23 nodes. Filter OpenRuna by integration to find related workflows and tools.
Can I import a sanitized export without credentials?
Yes. Use "Download sanitized JSON" to strip credential references before sharing internally. You will still add your own chat and lmChatOpenAi credentials in n8n after import.
What trigger type does "0864_Telegram_Splitout_Create_Triggered" use?
Trigger type: scheduled/triggered. After import, confirm the trigger node (webhook, schedule, or app event) matches your environment, then activate the workflow when you are ready to run it.
Is "0864_Telegram_Splitout_Create_Triggered" free to use?
OpenRuna catalogs community n8n workflows under open licenses. Check the source corpus link for the original license; commercial use may require verifying the third-party API terms for chat, lmChatOpenAi, outputParserStructured, telegram, openAi, limit, agent, splitOut.

Related resources