OpenRuna
Sign in
← Workflows

1276_Schedule_Telegram_Automation_Scheduled

14 nodes · lmChatOpenAi, schedule, chainSummarization, textSplitterRecursiveCharacterTextSplitter, openAi, telegram

Engine
n8n
Nodes
14
Trigger
scheduled/triggered
Source file
1276_Schedule_Telegram_Automation_Scheduled.json

Workflow flow

IntegrationsLmChatOpenAiScheduleChainSummarizationTextSplitterRecursiveCharacterTextSplitterOpenAITelegram@n8n/n8n-nodes-langchain.lmChatOpenAi@n8n/n8n-nodes-langchain.chainSummarization@n8n/n8n-nodes-langchain.textSplitterRecursiveCharacterTextSplitter@n8n/n8n-nodes-langchain.openAiSet
100%

OpenAI Chat Model

@n8n/n8n-nodes-langchain.lmChatOpenAi

TRIGGER

Schedule Trigger

Schedule

OpenAI Chat Model2

@n8n/n8n-nodes-langchain.lmChatOpenAi

Recursive Character Text Splitter

@n8n/n8n-nodes-langchain.textSplitterRecursiveCharacterTextSplitter

Config

Set

Create a story

@n8n/n8n-nodes-langchain.chainSummarization

Create a Prompt for DALL-E

@n8n/n8n-nodes-langchain.chainSummarization

Generate Audio for the story

@n8n/n8n-nodes-langchain.openAi

Send Story Text

Telegram

Generate a Picture for the story

@n8n/n8n-nodes-langchain.openAi

Send Audio for the story

Telegram

Send Story Picture

Telegram

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

Browse by integration

lmChatOpenAischedulechainSummarizationtextSplitterRecursiveCharacterTextSplitteropenAitelegram
Browse all integrations →
Download n8n JSONDownload sanitized JSONDownload flow graph

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

1276_Schedule_Telegram_Automation_Scheduled is a free n8n workflow on OpenRuna — 14 nodes connecting lmChatOpenAi, schedule, chainSummarization, textSplitterRecursiveCharacterTextSplitter, openAi, telegram. Download the JSON, view the flow diagram, and import it into your n8n instance.

What this workflow does

Built in n8n, "1276_Schedule_Telegram_Automation_Scheduled" chains 14 nodes to move data between lmChatOpenAi, schedule, chainSummarization, textSplitterRecursiveCharacterTextSplitter, openAi, telegram. 14 nodes · lmChatOpenAi, schedule, chainSummarization, textSplitterRecursiveCharacterTextSplitter, openAi, telegram Execution begins at the scheduled/triggered trigger and flows through the 14 configured nodes. OpenRuna renders the node graph and offers the JSON export so you can import and adapt it in minutes. Use it to learn integration patterns, fork it for your own use case, or deploy it quickly after reconnecting credentials.

Use cases

  • Fork it to add error handling, retries, or a notification step without designing the 14-node flow from scratch.
  • Benchmark it against your current lmChatOpenAi integration to spot missing steps or redundant nodes.
  • Study how data moves from lmChatOpenAi to schedule before building your own variant.
  • Share it with your team as a documented reference for scheduled/triggered automations in the lmChatOpenAi stack.

Example output

Imported into n8n, "1276_Schedule_Telegram_Automation_Scheduled" exposes 14 configured nodes. Trigger type: scheduled/triggered. Integrations: lmChatOpenAi, schedule, chainSummarization, textSplitterRecursiveCharacterTextSplitter, openAi, telegram. Set your credentials on the lmChatOpenAi node, then verify each downstream node picks them up. 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 "1276_Schedule_Telegram_Automation_Scheduled" JSON into a plain-English runbook, node by node. It can flag where lmChatOpenAi 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 lmChatOpenAi, schedule, chainSummarization, textSplitterRecursiveCharacterTextSplitter, openAi, telegram. Handy for onboarding teammates new to n8n.

Cursor

In Cursor, ask Agent mode to parameterise "1276_Schedule_Telegram_Automation_Scheduled" — extract lmChatOpenAi IDs and secrets into environment variables without changing the 14-node structure.

Frequently asked questions

How do I import "1276_Schedule_Telegram_Automation_Scheduled" 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 "1276_Schedule_Telegram_Automation_Scheduled" use?
It uses: lmChatOpenAi, schedule, chainSummarization, textSplitterRecursiveCharacterTextSplitter, openAi, telegram. The flow diagram above shows how each service connects across the 14 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 lmChatOpenAi and schedule credentials in n8n after import.
What trigger type does "1276_Schedule_Telegram_Automation_Scheduled" 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 "1276_Schedule_Telegram_Automation_Scheduled" 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 lmChatOpenAi, schedule, chainSummarization, textSplitterRecursiveCharacterTextSplitter, openAi, telegram.

Related resources