# Telegram Bot Token Sherlink
TG_SHERLINK_BOT_TOKEN=XXXXXXXX:XXXXXXXXXXXXXXXX
# Id Telegram Channel Sherlink
TG_SHERLINK_ID=-XXXXXXXXXXXXX
# Readeck server
READECK_SERVER=http://readeck.midomain.com
READECK_API_KEY=xxxxxxxxxxxxx
# Hoarder server
HOARDER_SERVER=http://hoarder.midomain.com
HOARDER_API_KEY=xxxxxxxxxxxxxx

n8n Workflow: Send Links from Telegram Channel to Hoarder and Readeck

This n8n workflow automates the process of extracting links from a Telegram channel and then forwarding them to two different services: Hoarder (for archiving) and Readeck (for reading later). It's designed to help you save interesting links found in Telegram channels for future reference and consumption.

What it does

This workflow performs the following steps:

1. Triggers on a Schedule: The workflow runs periodically based on a defined schedule.
2. Fetches Telegram Channel History: It makes an HTTP request to the Telegram Bot API to retrieve the latest messages from a specified channel.
3. Parses Messages for Links: It uses a Code node to process the fetched messages, extracting any URLs found within the message text.
4. Splits Links: If multiple links are found in a single message, the "Split Out" node separates them into individual items for further processing.
5. Prepares Data for Hoarder: It formats the extracted links into the structure required by the Hoarder API.
6. Sends Links to Hoarder: It makes an HTTP request to the Hoarder API to save the extracted links.
7. Prepares Data for Readeck: It formats the extracted links into the structure required by the Readeck API.
8. Sends Links to Readeck: It makes an HTTP request to the Readeck API to save the extracted links.

Prerequisites/Requirements

To use this workflow, you will need:

• n8n Instance: A running instance of n8n.
• Telegram Bot Token: A Telegram bot token to access the Telegram Bot API.
• Telegram Channel ID: The ID of the Telegram channel you want to monitor for links.
• Hoarder API Endpoint and Token: The API endpoint and an API token for your Hoarder instance.
• Readeck API Endpoint and Token: The API endpoint and an API token for your Readeck instance.

Setup/Usage

1. Import the Workflow: Import the provided JSON into your n8n instance.
2. Configure Credentials:
   • Telegram HTTP Request Node: Update the HTTP Request node (ID 19) with your Telegram Bot Token and the chat_id of your Telegram channel. You'll need to construct the URL for fetching messages (e.g., https://api.telegram.org/botYOUR_BOT_TOKEN/getChatHistory?chat_id=@YOUR_CHANNEL_USERNAME).
   • Hoarder HTTP Request Node: Update the HTTP Request node responsible for Hoarder with your Hoarder API endpoint and API token in the headers or body as required by your Hoarder setup.
   • Readeck HTTP Request Node: Update the HTTP Request node responsible for Readeck with your Readeck API endpoint and API token in the headers or body as required by your Readeck setup.
3. Configure Schedule Trigger: Adjust the "Schedule Trigger" node (ID 839) to your desired interval for checking the Telegram channel.
4. Review Code Node: The "Code" node (ID 834) contains JavaScript logic to extract URLs. You may need to review and adjust this if your Telegram messages have a unique structure or if you want to extract other types of information.
5. Activate the Workflow: Once configured, activate the workflow. It will start running automatically based on the defined schedule.