Weekly

Get a weekly list of your Fly.io apps

Each Monday you get every app in your organization with how many Machines it runs, where, and in what state.

Runs: Weekly
Apps: Fly.io
AI: Not needed
Access: org token (read)

Send this to your assistant

Create a ClickRuntime automation: every Monday at 9am, email me all apps in my Fly.io org 'acme' with their Machine count, regions and states.

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 Fly.io account tends to accumulate apps: a staging copy, a forgotten prototype, a worker someone launched for a test, a database nobody remembers. Each one with running Machines is a line on the bill, and teams discover them only when the invoice jumps. Without a list, no one is sure what is running, who owns it or whether it is still needed, and cleaning up feels risky. Few teams track it.

Every week, ClickRuntime lists the apps in your organization, then lists the Machines for each app, and emails you a table of apps with their Machine counts and states. It gives a clear picture of what runs on your account right now. It takes seconds to skim.

It is handy for small engineering teams and agencies hosting several client projects.

What you get out of it

Find forgotten apps before they cost money
A weekly list shows an old prototype with two running Machines. Stopping it saves money every month and removes something nobody remembers maintaining. Each forgotten Machine is a recurring charge you can end with one command.
Know what is deployed
Anyone joining the team can read the email and understand what exists on the account. That saves onboarding questions and avoids duplicated services. New hires get oriented faster, and the same question is not asked repeatedly in chat.
Control Machine counts
Seeing counts per app shows when a service scaled up and stayed there. Scaling back after a traffic spike prevents a quiet rise in monthly spend. A quiet rise in Machine counts can add up to a surprising amount over a year.
Support security reviews
Unmaintained apps are a risk because they run old dependencies. An inventory is the first step in deciding what to patch, what to retire and who owns each app. Owners can then be identified.
Keep a record of changes
Weekly emails can be compared to see what appeared or disappeared. That history helps explain a change in the bill or a surprising new service. Trends become obvious after a few weeks.

How it works

What happens, step by step

Every Monday, ClickRuntime lists every app in your Fly.io organization.
For each app it counts the Machines, notes which regions they run in and whether they are running or stopped.
You get one email with a line per app, like "api-prod: 4 Machines | regions ams, iad | 4 started".

Before it runs live

Connect Fly.io

What you get

RunsWeekly

Get a weekly list of your Fly.io appstoday, 9:00Succeeded

Email · Fly.io inventoryapi-prod: 4 Machines | regions ams, iad | 4 started staging: 2 Machines | regions ams | 2 stopped

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 Fly.io 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.pyexample

from collections import Counter
from clickruntime import on_trigger, credentials, http, notify

ORG = "acme"
API = "https://api.machines.dev/v1"

@on_trigger
def run(event):
    headers = {"Authorization": f"Bearer {credentials.secret('FLY_API_TOKEN')}"}
    apps = http.get(f"{API}/apps", params={"org_slug": ORG}, headers=headers).json()["apps"]
    lines = []
    for app in apps:
        machines = http.get(f"{API}/apps/{app['name']}/machines", headers=headers).json()
        regions = ", ".join(sorted({m["region"] for m in machines})) or "-"
        states = ", ".join(f"{n} {s}" for s, n in Counter(m["state"] for m in machines).items()) or "none"
        lines.append(f"{app['name']}: {len(machines)} Machines | regions {regions} | {states}")
    notify.email_me(f"Fly.io inventory for {ORG}: {len(apps)} apps", "\n".join(lines))
    return {"apps": len(apps)}

FAQ

Common questions

Does it include volumes and databases?

This inventory covers apps and their Machines. Volumes have a separate weekly snapshot check, and Postgres clusters appear as apps with Machines. You can ask for volume sizes to be added to the table. Ask for volumes if needed.

Do I need to name each app?

No. It lists every app in the organization you specify with its slug, so new apps appear automatically in the next email. You only provide the organization name and a Fly API token. New apps are included automatically.

Is the Fly token safe to use?

The token is stored as a secret in ClickRuntime and used to call the Machines and apps APIs. For safety, create a read-only or deploy-scoped token limited to the organization you want to list. Least privilege is the right default.

What permissions does it need?

org token (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.

On a schedule