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

Immich Docker Deployment Automation

Immich Docker Deployment Automation is a 34-node automation blueprint connecting SSH, Custom API via Webhook. Inspect its trigger, execution graph, branches, and implementation requirements.

SSHCustom API via Webhook

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.

34

Nodes

54

Links

1

Run groups

Connected tools

2 integrations

  • SSH
  • Custom API via Webhook

Canvas controls

Fit wide systems, then zoom into any run group.

Immich Docker Deployment Automation execution lanes1 run groups containing 32 workflow nodes and 49 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.API. trigger node, webhook. 0 incoming and 1 outgoing connections.STARTAPITRIGGERWEBHOOK0 IN / 1 OUTVersion. transform node, set. 0 incoming and 1 outgoing connections.STARTVersionTRANSFORMSET0 IN / 1 OUTUsers. transform node, set. 0 incoming and 1 outgoing connections.STARTUsersTRANSFORMSET0 IN / 1 OUTParametrs. transform node, set. 1 incoming and 1 outgoing connections.STEP 02ParametrsTRANSFORMSET1 IN / 1 OUTIf. decision node, if. 1 incoming and 4 outgoing connections.STEP 03IfDECISIONIF1 IN / 4 OUTIf1. decision node, if. 1 incoming and 2 outgoing connections.STEP 04If1DECISIONIF1 IN / 2 OUTContainer Stat. decision node, switch. 1 incoming and 4 outgoing connections.STEP 04Container StatDECISIONSWITCH1 IN / 4 OUT422-Invalid server domain. trigger node, respondToWebhook. 1 incoming and 0 outgoing connections.STEP 04422-Invalid server domainTRIGGERRESPONDTOWEBHOOK1 IN / 0 OUTContainer Actions. decision node, switch. 1 incoming and 7 outgoing connections.STEP 04Container ActionsDECISIONSWITCH1 IN / 7 OUTnginx. transform node, set. 1 incoming and 1 outgoing connections.STEP 05nginxTRANSFORMSET1 IN / 1 OUTInspect. transform node, set. 1 incoming and 1 outgoing connections.STEP 05InspectTRANSFORMSET1 IN / 1 OUTStat. transform node, set. 1 incoming and 1 outgoing connections.STEP 05StatTRANSFORMSET1 IN / 1 OUTLog. transform node, set. 1 incoming and 1 outgoing connections.STEP 05LogTRANSFORMSET1 IN / 1 OUTDependent containers Stat. transform node, set. 1 incoming and 1 outgoing connections.STEP 05Dependent containers StatTRANSFORMSET1 IN / 1 OUTStart. transform node, set. 1 incoming and 1 outgoing connections.STEP 05StartTRANSFORMSET1 IN / 1 OUTStop. transform node, set. 1 incoming and 1 outgoing connections.STEP 05StopTRANSFORMSET1 IN / 1 OUTMount Disk. transform node, set. 1 incoming and 1 outgoing connections.STEP 05Mount DiskTRANSFORMSET1 IN / 1 OUTUnmount Disk. transform node, set. 1 incoming and 1 outgoing connections.STEP 05Unmount DiskTRANSFORMSET1 IN / 1 OUTGET ACL. transform node, set. 1 incoming and 1 outgoing connections.STEP 05GET ACLTRANSFORMSET1 IN / 1 OUTSET ACL. transform node, set. 1 incoming and 1 outgoing connections.STEP 05SET ACLTRANSFORMSET1 IN / 1 OUTGET NET. transform node, set. 1 incoming and 1 outgoing connections.STEP 05GET NETTRANSFORMSET1 IN / 1 OUTDeploy-docker-compose. transform node, set. 1 incoming and 1 outgoing connections.STEP 06Deploy-docker-composeTRANSFORMSET1 IN / 1 OUTService Actions. decision node, switch. 2 incoming and 6 outgoing connections.STEP 07Service ActionsDECISIONSWITCH2 IN / 6 OUTTest Connection1. transform node, set. 1 incoming and 1 outgoing connections.STEP 08Test Connection1TRANSFORMSET1 IN / 1 OUTDeploy. transform node, set. 1 incoming and 1 outgoing connections.STEP 08DeployTRANSFORMSET1 IN / 1 OUTSuspend. transform node, set. 1 incoming and 1 outgoing connections.STEP 08SuspendTRANSFORMSET1 IN / 1 OUTUnsuspend. transform node, set. 1 incoming and 1 outgoing connections.STEP 08UnsuspendTRANSFORMSET1 IN / 1 OUTTerminated. transform node, set. 1 incoming and 1 outgoing connections.STEP 08TerminatedTRANSFORMSET1 IN / 1 OUTChangePackage. transform node, set. 1 incoming and 1 outgoing connections.STEP 08ChangePackageTRANSFORMSET1 IN / 1 OUTSSH. integration node, ssh. 19 incoming and 2 outgoing connections.STEP 09SSHINTEGRATIONSSH19 IN / 2 OUTCode1. transform node, code. 2 incoming and 1 outgoing connections.STEP 10Code1TRANSFORMCODE2 IN / 1 OUTAPI answer. trigger node, respondToWebhook. 1 incoming and 0 outgoing connections.OUTCOMEAPI answerTRIGGERRESPONDTOWEBHOOK1 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.Showing 32 of 34 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

API

49 Execution Links

  1. Start

    API

    Trigger

    Version

    Transform

    Users

    Transform

  2. Step 2

    Parametrs

    Transform

  3. Step 3

    If

    Decision

  4. Step 4

    If1

    Decision

    Container Stat

    Decision

    422-Invalid server domain

    Trigger

    Container Actions

    Decision

  5. Step 5

    nginx

    Transform

    Inspect

    Transform

    Stat

    Transform

    Log

    Transform

    Dependent containers Stat

    Transform

    Start

    Transform

    Stop

    Transform

    Mount Disk

    Transform

    Unmount Disk

    Transform

    GET ACL

    Transform

    SET ACL

    Transform

    GET NET

    Transform

  6. Step 6

    Deploy-docker-compose

    Transform

  7. Step 7

    Service Actions

    Decision

  8. Step 8

    Test Connection1

    Transform

    Deploy

    Transform

    Suspend

    Transform

    Unsuspend

    Transform

    Terminated

    Transform

    ChangePackage

    Transform

  9. Step 9

    SSH

    Integration

  10. Step 10

    Code1

    Transform

  11. Outcome

    API answer

    Trigger

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