The gap this fills: Docker Hub doesn't ship an official Telegram app. If you want image push to show up in Telegram the moment it happens, the usual options are a paid third-party bot, custom code, or routing everything through a $20–50/month automation platform just to move one webhook from one URL to another. ZestyGlue does exactly that one thing for $9/month.
What it looks like
ZestyGlue
Docker Hub — Image Pushed
myorg/myapp:v1.4.0
pushed by myorg
A real Docker Hub event, shown as ZestyGlue formats it for Telegram.
Setup — about two minutes
- Create the connector. In ZestyGlue, start a new Docker Hub → Telegram connector. You'll get a unique webhook URL right away.
- Point Docker Hub at it. In your repository, go to Webhooks, and paste in your ZestyGlue webhook URL. That's the only setting — Docker Hub's webhooks have no secret to configure.
- Point Telegram at ZestyGlue. Message @BotFather to create a bot and copy its token. Add the bot to your group or channel, then find its chat ID (e.g. via @userinfobot) and enter both into ZestyGlue.
Tip: Docker Hub's webhook fires on every push to the repository, including automated CI pushes — if you only want to know about release tags, consider a second repository just for tagged releases.
Events you can forward
image pushed
Questions
Does this work for private repositories?
Yes — Docker Hub's webhook feature works the same for private and public repositories, as long as you have admin access to configure it.
Will this fire for automated builds, not just manual pushes?
Yes, any push triggers the webhook, whether it came from docker push, a CI pipeline, or Docker Hub's own autobuild feature.
Does the bot need to be an admin in my group?
No, a regular member is enough for the bot to post messages. Admin rights are only needed for things like pinning messages, which ZestyGlue doesn't do.
What happens if my ZestyGlue subscription lapses?
Events are silently dropped rather than causing errors on Docker Hub's side — Docker Hub never sees a failure response, so it won't retry aggressively or flag your webhook as broken. Your dashboard will simply stop showing new events until you resubscribe.