OpenRuna
Sign in
← Workflows

puq-docker-immich-deploy

35 nodes · webhook, respondToWebhook, ssh, switch

Engine
n8n
Nodes
35
Trigger
scheduled/triggered
Source file
1966_Code_Webhook_Automation_Webhook.json

Workflow flow

IntegrationsWebhookRespondToWebhookSSHSwitchIFSetCode

Integration path in execution order (sticky notes and duplicate steps omitted)

IFSetWebhookRespondToWebhookCodeSSHSwitch

34 steps · use Full diagram for every node

Browse by integration

Browse all integrations →

Import into n8n

  1. Download the n8n JSON file (full or sanitized).
  2. In n8n: Workflows → Import from file.
  3. Open each node and reconnect credentials to your accounts.
  4. Test with manual execution before enabling triggers.

Sanitized JSON removes credential IDs — safer for sharing. Flow graph JSON is OpenRuna's lightweight format for diagrams and other tools, not n8n import.

View source corpus ↗

Overview

puq-docker-immich-deploy (35-node n8n automation, webhook, respondToWebhook, ssh, switch) is free on OpenRuna — view the graph and export the JSON to import into n8n.

What this workflow does

"puq-docker-immich-deploy" automates a webhook-to-respondToWebhook flow in n8n across 35 nodes. 35 nodes · webhook, respondToWebhook, ssh, switch Execution begins at the scheduled/triggered trigger and flows through the 35 configured nodes. On OpenRuna you get the visual graph, the integration list, and a downloadable JSON ready to import into n8n. Use it to learn integration patterns, fork it for your own use case, or deploy it quickly after reconnecting credentials.

Use cases

  • Share it with your team as a documented reference for scheduled/triggered automations in the webhook stack.
  • Study how data moves from webhook to respondToWebhook before building your own variant.
  • Use it as a starting template when wiring webhook, respondToWebhook, ssh, switch — adjust node parameters to your accounts and record IDs.
  • Import "puq-docker-immich-deploy" into n8n, reconnect credentials for webhook, respondToWebhook, ssh, switch, and run the same automation in your own workspace.

Example output

Imported into n8n, "puq-docker-immich-deploy" exposes 35 configured nodes. Trigger type: scheduled/triggered. Integrations: webhook, respondToWebhook, ssh, switch. Open each node after import to map credentials to your own webhook and respondToWebhook accounts. Run it once in test mode to verify any branch logic (Switch/IF nodes) before enabling production triggers.

Tips by platform

Claude

Paste the exported JSON for "puq-docker-immich-deploy" into Claude and ask it to explain each of the 35 nodes. Claude is good at suggesting credential mappings for webhook, respondToWebhook, ssh, switch, plus error-handling and idempotency improvements before you run it in production.

ChatGPT

Have ChatGPT generate a checklist for adapting "puq-docker-immich-deploy" to your accounts — which webhook, respondToWebhook, ssh, switch credentials to create and which node parameters to change first.

Cursor

Open the downloaded JSON in Cursor and use Agent mode to refactor hard-coded URLs into env vars, or to generate tests for any Code nodes. Keep the OpenRuna flow diagram open so you do not break connection order across the 35 nodes.

Frequently asked questions

How do I import "puq-docker-immich-deploy" into n8n?
Click Download n8n JSON on this page, then in n8n choose Workflows → Import from file and select the downloaded file. Reconnect credentials on each node — the export carries credential IDs from the original author's instance, not working secrets.
Which integrations does "puq-docker-immich-deploy" use?
It uses: webhook, respondToWebhook, ssh, switch. The flow diagram above shows how each service connects across the 35 nodes. Filter OpenRuna by integration to find related workflows and tools.
Can I import a sanitized export without credentials?
Yes. Use "Download sanitized JSON" to strip credential references before sharing internally. You will still add your own webhook and respondToWebhook credentials in n8n after import.
What trigger type does "puq-docker-immich-deploy" use?
Trigger type: scheduled/triggered. After import, confirm the trigger node (webhook, schedule, or app event) matches your environment, then activate the workflow when you are ready to run it.
Is "puq-docker-immich-deploy" free to use?
OpenRuna catalogs community n8n workflows under open licenses. Check the source corpus link for the original license; commercial use may require verifying the third-party API terms for webhook, respondToWebhook, ssh, switch.

Related resources