Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Workflow blueprintBrowse workflows
Schedule-Driven MonitoringIntermediate

Weekly Execution Monitoring and Notification

Weekly Execution Monitoring and Notification is a 6-node automation blueprint connecting Telegram, n8n executions. Inspect its trigger, execution graph, branches, and implementation requirements.

Telegramn8n executions

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.

6

Nodes

5

Links

1

Run groups

Connected tools

2 integrations

  • Telegram
  • n8n executions

Canvas controls

Fit wide systems, then zoom into any run group.

Weekly Execution Monitoring and Notification execution lanes1 run groups containing 6 workflow nodes and 5 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.Schedule Trigger. trigger node, scheduleTrigger. 0 incoming and 1 outgoing connections.STARTSchedule TriggerTRIGGERSCHEDULETRIGGER0 IN / 1 OUTGet all previous executions. integration node, n8n. 1 incoming and 1 outgoing connections.STEP 02Get all previous executionsINTEGRATIONN8N1 IN / 1 OUTFilter for executions of the week. decision node, filter. 1 incoming and 1 outgoing connections.STEP 03Filter for executions of …DECISIONFILTER1 IN / 1 OUTSet a message for each failed execution. transform node, set. 1 incoming and 1 outgoing connections.STEP 04Set a message for each fa…TRANSFORMSET1 IN / 1 OUTAggregate all messages. transform node, aggregate. 1 incoming and 1 outgoing connections.STEP 05Aggregate all messagesTRANSFORMAGGREGATE1 IN / 1 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.6 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

Schedule Trigger

5 Execution Links

  1. Start

    Schedule Trigger

    Trigger

  2. Step 2

    Get all previous executions

    Integration

  3. Step 3

    Filter for executions of the week

    Decision

  4. Step 4

    Set a message for each failed execution

    Transform

  5. Step 5

    Aggregate all messages

    Transform

  6. Outcome

    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