Trigger Coolify deployments from new Docker Hub and GHCR image digests
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 14 nodes and runs on a schedule (every day). It uses only n8n's built-in nodes.
How it runs
Trigger: On a schedule (every day).
- Set Docker Hub Variables (Edit Fields (Set)): sets 2 fields: repository_tag, coolify_UUID
- Set GHCR Variables (Edit Fields (Set)): sets 2 fields: repository_tag, coolify_UUID
- Split Docker Hub Repo Tags (Split Out): splits a list into separate items
- Split GHCR Repo Tags (Split Out): splits a list into separate items
- Fetch Docker Hub Tag Digest (HTTP Request): calls an HTTP API
- Fetch GHCR Auth Token (HTTP Request): calls an HTTP API
- Deduplicate Docker Hub Digests (Remove Duplicates): removes duplicate items
- Fetch GHCR OCI Index Digest (HTTP Request): calls an HTTP API (HEAD)
- Docker Hub Image Metadata (Edit Fields (Set)): sets 5 fields: registry, image, checked_at…
- Deduplicate GHCR Digests (Remove Duplicates): removes duplicate items
…plus 3 more steps. See the full node list below.
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (6)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - HTTP Request
n8n-nodes-base.httpRequest - Merge
n8n-nodes-base.merge - Remove Duplicates
n8n-nodes-base.removeDuplicates - Split Out
n8n-nodes-base.splitOut - Edit Fields (Set)
n8n-nodes-base.set
From the author
Quick overview 🔄 Monitor Container Images from Docker Hub or GHCR. This workflow checks Docker Hub or GitHub Container Registry (GHCR) image tags for new digests. When an update is detected, it calls your Coolify API to restart the mapped service so the…