Docker Hub pull and star count tracker for Google Sheets

PromptCreate

Every Monday at 7am, log a snapshot of my Docker Hub image statistics into a Google Sheet so I can track how each image grows over time. This is a deterministic logging job with no summarization: each weekly run simply appends a fresh set of rows that build a historical trend I can chart later.

First, use Docker Hub's List Repositories in a Namespace operation to fetch every repository in my namespace (my Docker ID for personal repositories, or my organization name for org-owned ones). Page through all results so no repository is missed.

For each repository returned, call Docker Hub's Get Repository operation to read its current pull_count and star_count.

Then, for each repository, append one row to my tracking Google Sheet using Google Sheets' Append Values operation. Each row should have four columns in this order: the date of this run as an ISO 8601 date, the repository name, the pull count, and the star count. Append one row per repository per run so the sheet stacks a new block of rows each week.

Only append; never overwrite or summarize existing rows. Keep the same four-column order every week so the growing history stays consistent and easy to chart. If the sheet already has a header row for date, repository, pull count, and star count, keep appending beneath it.

Example output

Date, Repository, Pull count, Star count 2026-07-20, my-org/api-gateway, 15230, 42 2026-07-20, my-org/worker, 8817, 19 2026-07-27, my-org/api-gateway, 15984, 44 2026-07-27, my-org/worker, 9102, 20

Additional information

What does this prompt do?

Runs automatically every Monday morning with no manual work.
Collects the current pull count and star count for every one of your Docker Hub images.
Adds a fresh, date-stamped row for each image to your Google Sheet.
Builds a week-by-week history you can turn into growth charts later.

What do I need to use this?

A Docker Hub account with the images you want to track.
A Google account and a Google Sheet to store the running history.
A simple column layout in that sheet for date, image, pull count, and star count.

How can I customize it?

Change the schedule if weekly is not the cadence you want, for example daily or the first of every month.
Point it at a different Google Sheet or tab whenever you like.
Track a whole organization's images instead of just your personal account by choosing a different namespace.

FAQs

How often does the tracker run?

By default it runs once a week, every Monday morning. You can change it to daily, monthly, or any schedule you prefer.

Will it overwrite the numbers I logged last week?

No. Each run adds new rows beneath your existing data, so your full week-by-week history stays intact and ready to chart.

Do I need to leave my computer running?

No. The workflow runs in the cloud on its schedule, so it keeps logging even when you are offline.

Can I track my organization's images instead of just my personal account?

Yes. Point it at your organization's namespace instead of your personal one and it will log every repository there.

What if I have a lot of images?

It works through all of your repositories automatically, adding one row for each of them every week.

Related templates

Log daily Mercury balances and alert when cash runs low

Every weekday morning, every account balance is logged to a spreadsheet, and you only hear about it in Slack when one drops below the limit you set.

Deterministic Code

Log Netlify form submissions to Sheets and email the team

Every contact and demo request from your Netlify site lands as a row in your tracking spreadsheet and as an email to your shared team inbox.

Deterministic Code

Auto-file completed Documenso contracts in Box and Sheets

When a contract finishes signing, the signed PDF and its certificate land in Box by quarter, your register updates and your ops channel hears about it.