Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Workflow blueprintBrowse workflows
Event-Driven AutomationIntermediate

Automated RSS to Telegram Alerts

Automated RSS to Telegram Alerts is a 11-node automation blueprint connecting RSS Feed, Telegram. Inspect its trigger, execution graph, branches, and implementation requirements.

RSS FeedTelegram

Interactive system map

Follow the runtime. Inspect what supports it.

Solid horizontal paths show main-channel execution. Violet dependencies sit beneath the exact step they configure or empower.

11

Nodes

10

Links

2

Run groups

Connected tools

2 integrations

  • RSS Feed
  • Telegram

Canvas controls

Fit wide systems, then zoom into any run group.

Automated RSS to Telegram Alerts execution lanes2 run groups containing 11 workflow nodes and 10 visible links. Solid horizontal lines are main-channel runtime links. Violet dashed lines connect typed dependencies beneath the runtime step they support. Focus any node to inspect its immediate path.Clear Function. transform node, function. 0 incoming and 0 outgoing connections.CORE RUNTIMEClear FunctionTRANSFORMFUNCTION0 IN / 0 OUTCron. integration node, cron. 0 incoming and 1 outgoing connections.STARTCronINTEGRATIONCRON0 IN / 1 OUTRSS Source. transform node, function. 1 incoming and 1 outgoing connections.STEP 02RSS SourceTRANSFORMFUNCTION1 IN / 1 OUTSplitInBatches. integration node, splitInBatches. 2 incoming and 1 outgoing connections.STEP 03SplitInBatchesINTEGRATIONSPLITINBATCHES2 IN / 1 OUTRSS Feed Read. integration node, rssFeedRead. 1 incoming and 2 outgoing connections.STEP 04RSS Feed ReadINTEGRATIONRSSFEEDREAD1 IN / 2 OUTonly get new RSS. transform node, function. 1 incoming and 1 outgoing connections.STEP 05only get new RSSTRANSFORMFUNCTION1 IN / 1 OUTIF-1. decision node, if. 1 incoming and 2 outgoing connections.STEP 06IF-1DECISIONIF1 IN / 2 OUTIF-2. decision node, if. 1 incoming and 2 outgoing connections.STEP 07IF-2DECISIONIF1 IN / 2 OUTTelegram_M365. Telegram node, telegram. 1 incoming and 0 outgoing connections.STEP 08Telegram_M365TELEGRAMTELEGRAM1 IN / 0 OUTTelegram_Security. Telegram node, telegram. 1 incoming and 0 outgoing connections.STEP 09Telegram_SecurityTELEGRAMTELEGRAM1 IN / 0 OUTTelegram_IT. Telegram node, telegram. 1 incoming and 0 outgoing connections.OUTCOMETelegram_ITTELEGRAMTELEGRAM1 IN / 0 OUT

Signal inspector

Focus, hover, or select a step to isolate its runtime and support links.

Main-channel runtimeTyped dependencytriggeraidecisiontransformintegration
Scroll horizontally to follow every connected flow.11 connected nodesEnter or click to lock · Escape to clear

Runtime breakdown

Read the execution spine before its dependencies.

Each run group separates main-channel steps from the models, tools, retrievers, and data services that support them. Start and outcome labels apply only to runtime nodes.

01

Run Group

Clear Function

0 Execution Links

  1. Core Runtime

    Clear Function

    Transform

02

Run Group

Cron

10 Execution Links

  1. Start

    Cron

    Integration

  2. Step 2

    RSS Source

    Transform

  3. Step 3

    SplitInBatches

    Integration

  4. Step 4

    RSS Feed Read

    Integration

  5. Step 5

    only get new RSS

    Transform

  6. Step 6

    IF-1

    Decision

  7. Step 7

    IF-2

    Decision

  8. Step 8

    Telegram_M365

    Integration

  9. Step 9

    Telegram_Security

    Integration

  10. Outcome

    Telegram_IT

    Integration

Turn the map into a plan

Adapt this blueprint to your company.

Bring the system shape into a workspace, then define the production controls, data boundaries, owners, and delivery sequence around your context.

Create a build planReturn to the atlas