OpenRuna
Sign in
← Workflows

0465_Telegram_Filter_Send_Scheduled

10 nodes · telegram, schedule, filter, n8n, aggregate

Engine
n8n
Nodes
10
Trigger
scheduled/triggered
Source file
0465_Telegram_Filter_Send_Scheduled.json

Workflow flow

IntegrationsTelegramScheduleFilterN8NAggregateSet
100%
TRIGGER

Schedule Trigger

Schedule

Get all previous executions

N8N

Filter for executions of the week

Filter

Set a message for each failed execution

Set

Aggregate all messages

Aggregate

Telegram

Telegram

6 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

0465_Telegram_Filter_Send_Scheduled (10-node n8n automation, telegram, schedule, filter, n8n, aggregate) is free on OpenRuna — view the graph and export the JSON to import into n8n.

What this workflow does

"0465_Telegram_Filter_Send_Scheduled" automates a telegram-to-schedule flow in n8n across 10 nodes. 10 nodes · telegram, schedule, filter, n8n, aggregate Execution begins at the scheduled/triggered trigger and flows through the 10 configured nodes. 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

  • Share it with your team as a documented reference for scheduled/triggered automations in the telegram stack.
  • Study how data moves from telegram to schedule before building your own variant.
  • Use it as a starting template when wiring telegram, schedule, filter, n8n, aggregate — adjust node parameters to your accounts and record IDs.
  • Import "0465_Telegram_Filter_Send_Scheduled" into n8n, reconnect credentials for telegram, schedule, filter, n8n, aggregate, and run the same automation in your own workspace.

Example output

Imported into n8n, "0465_Telegram_Filter_Send_Scheduled" exposes 10 configured nodes. Trigger type: scheduled/triggered. Integrations: telegram, schedule, filter, n8n, aggregate. Open each node after import to map credentials to your own telegram and schedule 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 "0465_Telegram_Filter_Send_Scheduled" into Claude and ask it to explain each of the 10 nodes. Claude is good at suggesting credential mappings for telegram, schedule, filter, n8n, aggregate, plus error-handling and idempotency improvements before you run it in production.

ChatGPT

Have ChatGPT generate a checklist for adapting "0465_Telegram_Filter_Send_Scheduled" to your accounts — which telegram, schedule, filter, n8n, aggregate 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 10 nodes.

Frequently asked questions

How do I import "0465_Telegram_Filter_Send_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 "0465_Telegram_Filter_Send_Scheduled" use?
It uses: telegram, schedule, filter, n8n, aggregate. The flow diagram above shows how each service connects across the 10 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 telegram and schedule credentials in n8n after import.
What trigger type does "0465_Telegram_Filter_Send_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 "0465_Telegram_Filter_Send_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 telegram, schedule, filter, n8n, aggregate.

Related resources