Skip to content

Automate Docker Hub

Track your Docker Hub repositories without refreshing them: new tags as they are pushed, which tags are current, how many pulls each image gets and which tags nobody uses any more. Push notices come in through a repository webhook, and the reports run on a schedule. Describe the report or alert to your AI assistant, approve what it lays out, and it keeps going on its own.

Try asking

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.

Build your own

Build any Docker Hub automation you can describe

The ideas above are ready-made starting points, not a fixed list. Describe what Docker Hub should do in your own words, with your conditions, other apps or an AI step, and 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.

For example, ask your assistant

Every day, check my Docker Hub repositories for images not pushed in 90 days and send me the list.

Every 30 minutes, check my Docker Hub repository for new tags and post the repo and tag to Slack.

Every week, check Docker Hub pull counts for my images, record them in Google Sheets, and post the week-over-week change to Slack.

Beyond chat

Have Docker Hub work when you're not in the chat

Connecting Docker Hub to ChatGPT or Claude lets you ask about it while you chat. ClickRuntime handles the part that should happen on its own: checks on a schedule and actions on each new event, set up from the same chat and running after you close it.

Setup

Connect Docker Hub

Docker Hub connects with your username and a personal access token you create. A read-only token covers every automation here.

Docker Hub

Developer / Container registry

  1. In Docker Hub, open Account settings and go to Personal access tokens.
  2. Click Generate new token, add a description, choose an expiration and set the access to Read-only.
  3. Click Generate and copy the token before leaving the page.
  4. In the ClickRuntime dashboard, open Connections & secrets and save your Docker Hub username and the token as secrets.

Good to know

Docker Hub limits that affect automations

  • The token is not sent to Docker Hub directly; each run trades your username and token for a short-lived login token, which is why both are needed.
  • Tokens have the expiration you picked, so the automations stop working when it passes until you add a new one.
  • Pulls are rate-limited by Docker Hub plan, but these automations read repository and tag details rather than pulling images.
  • The stale tag report only lists tags. Deleting them would need a token with Read, Write & Delete access.

FAQ

Questions about automating Docker Hub

What can ClickRuntime see on Docker Hub?
Your repositories and their tags, including push dates, last-pulled dates and pull counts, within whatever the token's access allows. With a read-only token it cannot change or delete anything.
Why does it need my username as well as the token?
Docker Hub does not accept a personal access token on its own. The username and token are exchanged for a short-lived token on every run, and that is what the API calls use.
How do push notifications work?
You add a webhook to the repository on Docker Hub once. Each push then sends the tag, the pusher and the repository name, and you get the message straight away.
Can it delete tags nobody pulls?
The ready automation only reports tags that have not been pulled in 90 days or have never been pulled. Removing them would need a token with delete rights, and you would have to ask for that step.
Does any of this need AI?
No. These are lookups and comparisons. If you want a plain-language weekly summary, it uses the AI that comes with ClickRuntime, with no key of your own.
Is this a Docker Hub connector for ChatGPT or Claude?
Not for chatting with Docker Hub data. A chat connector lets your assistant read and change Docker Hub while you're in the conversation. ClickRuntime is for the work that should happen without you: you set up an automation from the chat once, and it keeps running on a schedule or on each Docker Hub event.

Tell your assistant what Docker Hub should do

Free plan. No credit card.