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

Deep Work Cycle Management

Deep Work Cycle Management is a 18-node automation blueprint connecting Telegram, Google Sheets. Inspect its trigger, execution graph, branches, and implementation requirements.

TelegramGoogle Sheets

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.

18

Nodes

17

Links

2

Run groups

Connected tools

2 integrations

  • Telegram
  • Google Sheets

Canvas controls

Fit wide systems, then zoom into any run group.

Deep Work Cycle Management execution lanes2 run groups containing 18 workflow nodes and 17 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.Initiate Static Data. transform node, code. 0 incoming and 0 outgoing connections.CORE RUNTIMEInitiate Static DataTRANSFORMCODE0 IN / 0 OUTTelegram Trigger. Telegram node, telegramTrigger. 0 incoming and 1 outgoing connections.STARTTelegram TriggerTELEGRAMTELEGRAMTRIGGER0 IN / 1 OUTIf. decision node, if. 1 incoming and 2 outgoing connections.STEP 02IfDECISIONIF1 IN / 2 OUTstart or stop?. decision node, if. 1 incoming and 2 outgoing connections.STEP 03start or stop?DECISIONIF1 IN / 2 OUTInstructions Message. Telegram node, telegram. 1 incoming and 0 outgoing connections.STEP 03Instructions MessageTELEGRAMTELEGRAM1 IN / 0 OUTEnd of Session Notification. Telegram node, telegram. 1 incoming and 1 outgoing connections.STEP 04End of Session NotificationTELEGRAMTELEGRAM1 IN / 1 OUTClear Variables1. transform node, code. 1 incoming and 0 outgoing connections.STEP 05Clear Variables1TRANSFORMCODE1 IN / 0 OUTStart Cycle Notification. Telegram node, telegram. 2 incoming and 1 outgoing connections.STEP 06Start Cycle NotificationTELEGRAMTELEGRAM2 IN / 1 OUTDeep Work. integration node, wait. 1 incoming and 1 outgoing connections.STEP 07Deep WorkINTEGRATIONWAIT1 IN / 1 OUTShort Break Notification. Telegram node, telegram. 1 incoming and 1 outgoing connections.STEP 08Short Break NotificationTELEGRAMTELEGRAM1 IN / 1 OUTBreak. integration node, wait. 1 incoming and 1 outgoing connections.STEP 09BreakINTEGRATIONWAIT1 IN / 1 OUTIncrement Count. transform node, code. 1 incoming and 1 outgoing connections.STEP 10Increment CountTRANSFORMCODE1 IN / 1 OUTBack to Work Notification. Telegram node, telegram. 1 incoming and 2 outgoing connections.STEP 11Back to Work NotificationTELEGRAMTELEGRAM1 IN / 2 OUTRecord Deep Work. Google Sheets node, googleSheets. 1 incoming and 0 outgoing connections.STEP 12Record Deep WorkGOOGLE SHEETSGOOGLESHEETS1 IN / 0 OUT< 4 Cycles. decision node, if. 1 incoming and 2 outgoing connections.STEP 13< 4 CyclesDECISIONIF1 IN / 2 OUTLong Break Notification. Telegram node, telegram. 1 incoming and 2 outgoing connections.STEP 14Long Break NotificationTELEGRAMTELEGRAM1 IN / 2 OUTRecord Long Break. Google Sheets node, googleSheets. 1 incoming and 0 outgoing connections.STEP 15Record Long BreakGOOGLE SHEETSGOOGLESHEETS1 IN / 0 OUTClear Variables2. transform node, code. 1 incoming and 0 outgoing connections.OUTCOMEClear Variables2TRANSFORMCODE1 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.18 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

Initiate Static Data

0 Execution Links

  1. Core Runtime

    Initiate Static Data

    Transform

02

Run Group

Telegram Trigger

17 Execution Links

  1. Start

    Telegram Trigger

    Trigger

  2. Step 2

    If

    Decision

  3. Step 3

    start or stop?

    Decision

    Instructions Message

    Integration

  4. Step 4

    End of Session Notification

    Integration

  5. Step 5

    Clear Variables1

    Transform

  6. Step 6

    Start Cycle Notification

    Integration

  7. Step 7

    Deep Work

    Integration

  8. Step 8

    Short Break Notification

    Integration

  9. Step 9

    Break

    Integration

  10. Step 10

    Increment Count

    Transform

  11. Step 11

    Back to Work Notification

    Integration

  12. Step 12

    Record Deep Work

    Integration

  13. Step 13

    < 4 Cycles

    Decision

  14. Step 14

    Long Break Notification

    Integration

  15. Step 15

    Record Long Break

    Integration

  16. Outcome

    Clear Variables2

    Transform

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