Weekly

Get a weekly list of your Heroku apps and dynos

Each Monday you see every app with its dyno types and counts, which makes forgotten apps easy to spot.

Runs: Weekly
Apps: Heroku
AI: Not needed
Access: read

Send this to your assistant

Create a ClickRuntime automation: every Monday at 8am email me all my Heroku apps with their dyno formation: process type, size and quantity.

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

Heroku makes it easy to start apps and just as easy to forget them. A contractor spins up a demo, a feature branch gets its own review app, a staging environment is scaled to Performance dynos for a load test and left there. Each one quietly bills by the hour. Engineering managers usually find out in the monthly invoice, when a $250 app that nobody uses has been running since June.

Each week, the apps in your Heroku account are listed and the formation for each is read, which shows the process types, dyno sizes and quantities. An email lists every app with what it is running, so oversized and orphaned apps stand out.

It is useful for engineering leads and agencies that host many client apps and want a regular, readable inventory.

What you get out of it

Oversized dynos are noticed
A Performance-L left running on a staging app is obvious when the whole list is in one email. Scaling it down is a one-minute fix with a clear saving. That adds up quickly when the oversized process is billed every hour.
Orphaned apps are found
Demos and abandoned prototypes show up with their dynos still running. You can delete or scale them to zero before they cost another month. Catching them weekly means they cost one week of billing, not six months of it.
New apps are seen as they appear
A weekly view shows apps created since last time, so a stray review app or a contractor's test environment does not stay hidden. Each is a small, early chance to ask who made it and whether it should still exist.
Handovers and audits are simpler
When a team member leaves or a client asks what is running, you have a dated list showing apps, process types and sizes without logging in to each. Auditors and clients get a straight answer without anyone clicking through every app.
A habit of right-sizing
Reading the list weekly makes dyno size a conscious choice, and teams drift less toward the biggest option when in doubt. Over a quarter that habit lowers the bill without any dramatic cost-cutting project.

How it works

What happens, step by step

Every Monday ClickRuntime lists all your Heroku apps.
For each app it gets the dyno types, how many of each and their sizes.
The list arrives in your inbox, making forgotten apps easy to spot.

Before it runs live

Connect Heroku

What you get

RunsWeekly

Get a weekly list of your Heroku apps and dynostoday, 9:00Succeeded

Email · Heroku inventoryshop-api-prod: web 2x standard-2X, worker 1x standard-1X shop-admin: web 1x basic

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

Run it at a different time, more or less often, or only on weekdays
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 Heroku 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_a_weekly_inventory_of_apps_and_dynos.pyexample

from clickruntime import on_trigger, credentials, http, notify

HEROKU = "https://api.heroku.com"

def heroku(path, **headers):
    resp = http.get(f"{HEROKU}{path}", headers={"Accept": "application/vnd.heroku+json; version=3",
                    "Authorization": f"Bearer {credentials.secret('HEROKU_API_KEY')}", **headers})
    resp.raise_for_status()
    return resp.json()

@on_trigger
def run(event):
    lines = []
    for app in heroku("/apps"):
        formation = heroku(f"/apps/{app['id']}/formation")
        dynos = ", ".join(f"{f['type']} {f['quantity']}x {f['size']}" for f in formation) or "no dynos"
        lines.append(f"{app['name']}: {dynos}")
    notify.email_me(f"Heroku inventory: {len(lines)} apps", "\n".join(lines))
    return {"apps": len(lines)}

FAQ

Common questions

What does the formation show?

For each app, the process types such as web and worker, their dyno size and the quantity. That is enough to spot a scaled-up process or a worker nobody needs anymore. Together they show how each app is scaled.

Will it change or scale anything?

No. It reads only. Scaling or deleting is a decision for a person, so nothing is changed by the report, and a forgotten app is brought to your attention and left alone. Review is a human decision, and the report only supports it.

Can it flag only dynos above a certain size?

Yes. A filter for sizes above Standard-2X, for example, shortens the list to what needs a second look. Ask for it in plain words and approve the change before it runs. The report then stays short enough to read in a minute.

What permissions does it need?

read. 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 each time it runs (weekly). Checks that find nothing to do and stop right away aren't counted.

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.

Monthly