The moment it happens

Get a message when a new tag is pushed

Each time a tag is pushed to your repository, you see the tag, who pushed it and the repo right away.

Runs: The moment it happens
Apps: Docker Hub
AI: Not needed
Access: webhook set up in the repo (one-time)

Send this to your assistant

Create a ClickRuntime automation: give me a webhook link for my Docker Hub repo acme/api. When a new tag is pushed, post the tag, the pusher and the repo name to #releases in Slack.

Paste it into your assistant. It tells you what it will send or change before it runs live.

Add to ChatGPT Add to Claude

First time? Adding ClickRuntime to your assistant takes about two minutes.

Why use it

Why teams use this automation

A team that relies on a shared base image, or a customer waiting for a hotfix tag, needs to know when a new version is pushed to Docker Hub. Without a notice, someone refreshes the repository page or finds out a day later when a deployment pulls the wrong thing. A push by a colleague, a CI job or an unexpected account can pass unnoticed, which matters when images go straight into production.

When a tag is pushed, Docker Hub sends a webhook with the push details. The automation receives it and posts the tag name, who pushed it and which repository it belongs to into your channel, within moments of the push completing.

Platform teams, release managers and maintainers of public images use it to follow publishing activity as it happens.

What you get out of it

Everyone learns of a release at once
A post in the channel means the team and any support staff know the version is out. Nobody asks whether the hotfix has shipped, because the answer is already visible to everyone who needs it.
Unexpected pushes are caught quickly
Seeing who pushed a tag makes an unfamiliar account or a push at an odd hour obvious. That gives you time to investigate before the image is deployed anywhere, which matters most for images that run in production.
Deployments can follow immediately
Teams that deploy after a new tag appears can act within minutes. The notification replaces refreshing the page, so rollouts start as soon as the image is ready and not whenever someone next looks.
A running log of publishing activity
The channel records every push with the tag and the pusher. That is useful for retracing what happened around an incident, since you can scroll back to the exact time an image changed.
Less polling of Docker Hub
No script has to check repeatedly for a new tag. The event arrives when something happens, which means nothing is checked needlessly and there is no delay waiting for the next scheduled poll.

How it works

What happens, step by step

Each time someone pushes a tag to your Docker Hub repository, Docker Hub tells ClickRuntime straight away.
It picks out the repository, the new tag and who pushed it.
A message goes to #releases, like "New image pushed: acme/api:v2.14.0 by acme-ci".

Before it runs live

Connect Docker Hub
Paste your automation's link into the other app's webhook settings

What you get

RunsThe moment it happens

Get a message when a new tag is pushedjust nowSucceeded

Slack · #releasesNew image pushed: acme/api:v2.14.0 by acme-ci

Build your own

Need it to work differently?

This template is a starting point. Copy the prompt and change it, or describe a different automation from scratch, with your own conditions, more apps or an AI step. Your assistant writes it, tests it and runs it on ClickRuntime.

Your own rules
Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.
Any number of apps
One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.
AI where it helps
Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.
On a schedule or on each event
Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

Changes you can ask for

Act only on the items that match your own rules, and skip the rest
Add an AI step, for example to summarize, sort or draft a reply
Add another app, for example also send it to Slack
Combine it with other Docker Hub steps into one automation

Under the hood

The code that runs this automation

This is the Python script that runs each time the automation starts. Your AI assistant writes it for you when you send the prompt, and you allow each step in your assistant. To change how the automation works, describe the change to your assistant and it updates the script for you. For every function it can use, see the script reference.

get_notified_of_new_image_pushes.pyexample

from clickruntime import on_event, notify

@on_event
def handle(event):
    body = event.json or {}
    push = body.get("push_data", {})
    repo = body.get("repository", {}).get("repo_name")
    if not push.get("tag"):
        return {"skipped": "no tag in payload"}
    notify.slack(f"New image pushed: {repo}:{push['tag']} by {push.get('pusher', 'unknown')}",
                 channel="#releases")
    return {"repo": repo, "tag": push["tag"]}

FAQ

Common questions

How do I connect Docker Hub to it?

In the repository settings on Docker Hub, add a webhook and paste the ClickRuntime webhook address. Docker Hub then sends an event each time a tag is pushed, and no polling is needed on either side.

Does it fire for every tag, including latest?

Yes. Every push triggers an event, including a repeated push of an existing tag such as latest. If that is too noisy, tell your AI assistant to post only for tags that match a pattern, such as version numbers.

What information appears in the message?

The message shows the repository, the tag and the name of the account that pushed it, and can link to the repository page. Those come from the push details that Docker Hub includes in the event it sends.

What permissions does it need?

webhook set up in the repo (one-time). Nothing else in your accounts is used.

Does it need AI?

No. It runs without AI, so it doesn't use your plan's AI allowance.

How many runs does it use?

One run for each event the app sends.

Can I change how it works?

Yes. Describe the change to your AI assistant, for example a different schedule, channel or filter. It updates the automation, tests it and tells you what changed.

Weekly