Telegram channel to Readeck & Hoarder
15 nodes · schedule, splitOut, httpRequest
- Engine
- n8n
- Nodes
- 15
- Trigger
- scheduled/triggered
- Source file
- 1468_Splitout_Code_Automation_Webhook.json
Workflow flow
Schedule Trigger
Schedule
channel_items_tg
HTTP
channel_links_tg
Code
get_links_rd
HTTP
get_links_hd
HTTP
Split Out
Split Out
saved_links_rd
Set
not_saved_links_rd
Code
saved_links_hd
Set
not_saved_links_hd
Code
save_link_rd
HTTP
save_link_hd
HTTP
12 steps · flows top to bottom, branches left to right
Browse by integration
Browse all integrations →Import into n8n
- Download the n8n JSON file (full or sanitized).
- In n8n: Workflows → Import from file.
- Open each node and reconnect credentials to your accounts.
- 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.
Overview
Telegram channel to Readeck & Hoarder (15-node n8n automation, schedule, splitOut, httpRequest) is free on OpenRuna — view the graph and export the JSON to import into n8n.
What this workflow does
"Telegram channel to Readeck & Hoarder" is an n8n automation built from 15 nodes spanning schedule, splitOut, httpRequest. 15 nodes · schedule, splitOut, httpRequest A scheduled/triggered entry point kicks it off, and each node passes data to the next until the run completes. 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
- Use it as a starting template when wiring schedule, splitOut, httpRequest — adjust node parameters to your accounts and record IDs.
- Import "Telegram channel to Readeck & Hoarder" into n8n, reconnect credentials for schedule, splitOut, httpRequest, and run the same automation in your own workspace.
- Share it with your team as a documented reference for scheduled/triggered automations in the schedule stack.
- Study how data moves from schedule to splitOut before building your own variant.
Example output
Imported into n8n, "Telegram channel to Readeck & Hoarder" exposes 15 configured nodes. Trigger type: scheduled/triggered. Integrations: schedule, splitOut, httpRequest. Open each node after import to map credentials to your own schedule and splitOut accounts. Run it once in test mode to verify any branch logic (Switch/IF nodes) before enabling production triggers.
Tips by platform
Claude
Paste the exported JSON for "Telegram channel to Readeck & Hoarder" into Claude and ask it to explain each of the 15 nodes. Claude is good at suggesting credential mappings for schedule, splitOut, httpRequest, plus error-handling and idempotency improvements before you run it in production.
ChatGPT
Have ChatGPT generate a checklist for adapting "Telegram channel to Readeck & Hoarder" to your accounts — which schedule, splitOut, httpRequest credentials to create and which node parameters to change first.
Cursor
Open the downloaded JSON in Cursor and use Agent mode to refactor hard-coded URLs into env vars, or to generate tests for any Code nodes. Keep the OpenRuna flow diagram open so you do not break connection order across the 15 nodes.
Frequently asked questions
- How do I import "Telegram channel to Readeck & Hoarder" 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 "Telegram channel to Readeck & Hoarder" use?
- It uses: schedule, splitOut, httpRequest. The flow diagram above shows how each service connects across the 15 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 schedule and splitOut credentials in n8n after import.
- What trigger type does "Telegram channel to Readeck & Hoarder" 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 "Telegram channel to Readeck & Hoarder" 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 schedule, splitOut, httpRequest.
Related resources
- Agent
PraisonAI
24/7 AI employee team for automating complex challenges. Low-code multi-agent framework with handoffs, guardrails, memory, RAG, and 100+ LLM providers
- Agent
Prompt Optimizer
AI prompt optimization tool with multi-round iterative improvements, dual-mode optimization for system and user prompts, and multi-model support. Available as web app, desktop app, Chrome extension, and Docker deployment. AGPL-3.0 licensed
- Agent
Archon
Workflow engine for deterministic AI coding agents. Define development processes as YAML workflows (planning → implementation → validation → review → PR) with isolated Git worktrees for parallel execution. MIT licensed
- Agent
A2A Protocol
Agent2Agent (A2A) open protocol enabling communication and interoperability between opaque agentic applications. Donated to Linux Foundation by Google with 50+ technology partners. Apache 2.0 licensed
- Agent
CAMEL
First and best multi-agent framework for building scalable agent systems. Apache 2.0 licensed with extensive tooling for agent communication and task automation
- Agent
Neuron AI
PHP Agentic Framework for building production-ready AI driven applications. Connect components (LLMs, vector DBs, memory) to agents that can interact with your data. MIT licensed
- Agent
smolagents
Lightweight agent framework centered on tool use and code-executing workflows
- Agent
Supermemory
Memory API and app for AI agents that provides fast, scalable, context-aware storage and retrieval across projects. MIT licensed
