🔄 Monitor Container Images from Docker Hub and GHCR to Trigger Coolify Deployments

Built with n8n
1

This workflow monitors container image registries for new digests and triggers a deployment whenever an update is detected. It supports Docker Hub and GitHub Container Registry (GHCR), making it easy to keep self-hosted apps up to date.

Who’s it for

DevOps engineers, homelab enthusiasts, and developers who manage self-hosted applications using container images and want to automate update detection without manually checking registries.

How it works

  • Runs on a schedule to check for new image versions.
  • Defines repository tags and deployment IDs for Docker Hub and GHCR images.
  • Fetches the latest image digest from each registry (handling GHCR auth tokens).
  • Removes digests already seen in previous runs.
  • Builds a standardized metadata object for each new update.
  • Merges both branches and triggers a deployment API call (e.g., restarting a Coolify service).

Requirements

  • Registry image references for the images you want to monitor.
  • Authentication credentials for your deployment platform API.

How to set up

  1. Configure the Schedule Trigger to set how often checks run.
  2. Open the “Set Variables” nodes, add your repository_tag arrays, and match them with your deployment IDs. Ensure the order corresponds by index (e.g., the first image maps to the first UUID, the second image to the second UUID, and so on).
  3. Open the final HTTP Request node and replace the URL and authentication with your own deployment platform (Coolify, Portainer, Kubernetes, etc.).

How to customize

  • Add more images by extending the repository lists in the Variables nodes.
  • Replace the final deployment step with Portainer, Docker Swarm, or a custom webhook.
  • Add notifications (e.g., Slack, Discord) or approval steps before deployment.
1 Like