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

Automated n8n Update and Notification Workflow

Automated n8n Update and Notification Workflow is a 14-node automation blueprint connecting SSH, GitHub, Telegram. Inspect its trigger, execution graph, branches, and implementation requirements.

SSHGitHubTelegram

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.

14

Nodes

15

Links

1

Run groups

Connected tools

3 integrations

  • SSH
  • GitHub
  • Telegram

Canvas controls

Fit wide systems, then zoom into any run group.

Automated n8n Update and Notification Workflow execution lanes1 run groups containing 14 workflow nodes and 15 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 OUTWhen clicking ‘Test workflow’. trigger node, manualTrigger. 0 incoming and 1 outgoing connections.STARTWhen clicking ‘Test workf…TRIGGERMANUALTRIGGER0 IN / 1 OUTSet Default variable. transform node, set. 2 incoming and 2 outgoing connections.STEP 02Set Default variableTRANSFORMSET2 IN / 2 OUTcheck n8n installed version. integration node, ssh. 1 incoming and 1 outgoing connections.STEP 03check n8n installed versionINTEGRATIONSSH1 IN / 1 OUTGithub HTTP Request. GitHub node, httpRequest. 1 incoming and 1 outgoing connections.STEP 03Github HTTP RequestGITHUBHTTPREQUEST1 IN / 1 OUTEdit Version String. transform node, set. 1 incoming and 1 outgoing connections.STEP 04Edit Version StringTRANSFORMSET1 IN / 1 OUTMerge Results. decision node, merge. 2 incoming and 1 outgoing connections.STEP 05Merge ResultsDECISIONMERGE2 IN / 1 OUTComapre Two Input. decision node, if. 2 incoming and 2 outgoing connections.STEP 06Comapre Two InputDECISIONIF2 IN / 2 OUTTelegram Notif. Telegram node, telegram. 1 incoming and 0 outgoing connections.STEP 07Telegram NotifTELEGRAMTELEGRAM1 IN / 0 OUTTelegram Approve. Telegram node, telegram. 1 incoming and 1 outgoing connections.STEP 08Telegram ApproveTELEGRAMTELEGRAM1 IN / 1 OUTPull n8n Image. integration node, ssh. 1 incoming and 1 outgoing connections.STEP 09Pull n8n ImageINTEGRATIONSSH1 IN / 1 OUTdocker compose pull. integration node, ssh. 1 incoming and 1 outgoing connections.STEP 10docker compose pullINTEGRATIONSSH1 IN / 1 OUTdocker compose up. integration node, ssh. 1 incoming and 1 outgoing connections.STEP 11docker compose upINTEGRATIONSSH1 IN / 1 OUTTelegram Notif1. Telegram node, telegram. 1 incoming and 1 outgoing connections.OUTCOMETelegram Notif1TELEGRAMTELEGRAM1 IN / 1 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.14 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

15 Execution Links

  1. Start

    Schedule Trigger

    Trigger

    When clicking ‘Test workflow’

    Trigger

  2. Step 2

    Set Default variable

    Transform

  3. Step 3

    check n8n installed version

    Integration

    Github HTTP Request

    Integration

  4. Step 4

    Edit Version String

    Transform

  5. Step 5

    Merge Results

    Decision

  6. Step 6

    Comapre Two Input

    Decision

  7. Step 7

    Telegram Notif

    Integration

  8. Step 8

    Telegram Approve

    Integration

  9. Step 9

    Pull n8n Image

    Integration

  10. Step 10

    docker compose pull

    Integration

  11. Step 11

    docker compose up

    Integration

  12. Outcome

    Telegram Notif1

    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