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

Daily RSS to Telegram and Email Alert

Daily RSS to Telegram and Email Alert is a 7-node automation blueprint connecting Telegram, AWS SES. Inspect its trigger, execution graph, branches, and implementation requirements.

TelegramAWS SES

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.

7

Nodes

6

Links

1

Run groups

Connected tools

2 integrations

  • Telegram
  • AWS SES

Canvas controls

Fit wide systems, then zoom into any run group.

Daily RSS to Telegram and Email Alert execution lanes1 run groups containing 7 workflow nodes and 6 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.On clicking 'execute'. trigger node, manualTrigger. 0 incoming and 1 outgoing connections.STARTOn clicking 'execute'TRIGGERMANUALTRIGGER0 IN / 1 OUTCron. integration node, cron. 0 incoming and 1 outgoing connections.STARTCronINTEGRATIONCRON0 IN / 1 OUTRSS Feed Read. integration node, rssFeedRead. 2 incoming and 1 outgoing connections.STEP 02RSS Feed ReadINTEGRATIONRSSFEEDREAD2 IN / 1 OUTFilter by current day. transform node, function. 1 incoming and 1 outgoing connections.STEP 03Filter by current dayTRANSFORMFUNCTION1 IN / 1 OUTIF. decision node, if. 1 incoming and 2 outgoing connections.STEP 04IFDECISIONIF1 IN / 2 OUTAWS SES. integration node, awsSes. 1 incoming and 0 outgoing connections.OUTCOMEAWS SESINTEGRATIONAWSSES1 IN / 0 OUTTelegram. Telegram node, telegram. 1 incoming and 0 outgoing connections.OUTCOMETelegramTELEGRAMTELEGRAM1 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.7 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

On clicking 'execute'

6 Execution Links

  1. Start

    On clicking 'execute'

    Trigger

    Cron

    Integration

  2. Step 2

    RSS Feed Read

    Integration

  3. Step 3

    Filter by current day

    Transform

  4. Step 4

    IF

    Decision

  5. Outcome

    AWS SES

    Integration

    Telegram

    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