← All N8N workflows
Messaging & emailCodeHTTP RequestSchedule TriggerEdit FieldsSplit Out

Telegram channel to Readeck & Hoarder

Configured with HTTP Request, Schedule Trigger, Split Out. Review the connections and setup before adapting this template.

Workflow preview
TriggerSchedule TriggerSchedule TriggerTransformSplit OutSplit OutCodenot_saved_links_hdCodeCodenot_saved_links_rdCodeTransformsaved_links_rdEdit FieldsWeb / APIsave_link_rdHTTP RequestWeb / APIsave_link_hdHTTP RequestWeb / APIget_links_rdHTTP RequestWeb / APIget_links_hdHTTP RequestTransformsaved_links_hdEdit FieldsCodechannel_links_tgCodeWeb / APIchannel_items_tgHTTP Request

Node categories in this workflow

  • Trigger
  • Transform
  • Code
  • 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.

Workflow node names, types, and operations
NodeCategoryTypeOperation
Schedule TriggerTriggerSchedule TriggerSee node parameters
Split OutTransformSplit OutSee node parameters
not_saved_links_hdCodeCodeSee node parameters
not_saved_links_rdCodeCodeSee node parameters
saved_links_rdTransformEdit FieldsSee node parameters
save_link_rdWeb / APIHTTP RequestPOST
save_link_hdWeb / APIHTTP RequestPOST
get_links_rdWeb / APIHTTP RequestSee node parameters
get_links_hdWeb / APIHTTP RequestSee node parameters
saved_links_hdTransformEdit FieldsSee node parameters
channel_links_tgCodeCodeSee node parameters
channel_items_tgWeb / APIHTTP RequestSee node parameters

Setup

  1. Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
  2. Connect your own credentials through n8n’s credential store. Replace REPLACE_WITH_* values with your resource identifiers.
  3. Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
  4. 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

Telegram channel to Readeck & Hoarder

Telegram channel to Readeck & Hoarder

Purpose and structure

This folder contains the Telegram channel to Readeck & Hoarder workflow. Its executable nodes use code, httpRequest, scheduleTrigger, set, splitOut. 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

Schedule 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/Splitout/1468_Splitout_Code_Automation_Webhook.json MIT; preserve source notices.

Canvas section labels

These name areas of the original canvas; they do not include explanatory instructions.

  • Readeck
  • Telegram
  • Hoarder

More in Messaging & email