Skip to content
ClickRuntime

Automate Fly.io

Fly.io runs your apps as Machines spread across regions, with volumes for anything that has to persist. ClickRuntime keeps an eye on that setup for you: it spots Machines that stopped or failed, lists your apps and regions every week, parks staging Machines overnight, and checks that volume snapshots are recent. Say what you need to your AI assistant, look over what it proposes, and it runs on schedule from then on.

Add to ChatGPTAdd to Claude
Works inChatGPTClaudeClaude CodeCursorCodexVS CodeGemini CLIZedopencodeAny MCP client

Try asking

Create a ClickRuntime automation: every 5 minutes, check the Machines in my Fly app 'api-prod' and post to #ops in Slack if any is no longer started. Ignore the Machines in 'preview-web', which autostop.

Paste it into your assistant. It tells you what it will send or change before it runs live.

Ideas

What you can automate in Fly.io

Word when a Machine stops or fails, a weekly inventory of apps by region and state, staging that sleeps outside working hours, and proof your volumes have fresh snapshots. These are ready-made starting points. Anything else you can describe works too.
Every 5 minutes

Hear in Slack when a Fly Machine stops or fails

If a Machine in your app leaves the started state, your channel gets one message naming it and its region.

See how it works
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.

See how it works
On a schedule

Shut down staging Machines overnight

Staging Machines stop in the evening and start again before work, and you only get an email if one refuses.

See how it works
Weekly

Check that your Fly volumes have recent snapshots

Once a week you see the newest snapshot date for each volume, with any that are falling behind flagged.

See how it works Your own logic

Any other automation you can describe in words

Your own rules, schedule and AI steps with Fly.io, plus any other app. Describe it and your assistant builds it.

See how to build your own

Build your own

Build any Fly.io automation you can describe

The ideas above are ready-made starting points, not a fixed list. Describe what Fly.io 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 10 minutes, check my Fly.io machines and start any that stopped unexpectedly, then tell me which ones.

Every morning, post the status of each Fly.io app and region to Slack.

Every day, check my Fly.io apps' machine count and health checks, log them in Google Sheets, and email me from Gmail if any app has failing checks.

Beyond chat

Have Fly.io work when you're not in the chat

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

Fly.io connects with an access token you create yourself, either for a whole organization or for one app. Pick the narrowest one that covers the automation.

Fly.io

Developer / Hosting

  1. For a whole organization, run fly tokens create org -o <org-slug> --expiry 8760h.
  2. For a single app, run fly tokens create deploy -a <app> instead. You can also create a token in the Fly.io dashboard under Account, then Access Tokens.
  3. Copy the token value without any Bearer or FlyV1 prefix in front of it.
  4. In the ClickRuntime dashboard, open Connections & secrets and save it as a secret for Fly.io.

Good to know

Fly.io limits that affect automations

  • Fly.io tokens last 20 years unless you set an expiry, so pass --expiry when creating one.
  • An app-scoped deploy token only sees that one app. Weekly inventories across apps need an org token.
  • Listing apps requires your organization slug, so keep it handy when you set up an inventory.
  • Machines with autostop turned on show as stopped when idle, and Fly Proxy can start them again when traffic arrives. Exclude them from crash alerts and expect them to wake up after a scheduled stop.

FAQ

Questions about automating Fly.io

What can ClickRuntime see and change on Fly.io?
It works through the Machines API with your token. It can list apps, Machines, volumes and snapshots, and start or stop Machines. An org token covers the organization, a deploy token covers one app.
Will autostopped Machines trigger false alerts?
They can, because an idle autostopped Machine reports as stopped. Tell your assistant which apps or Machines scale to zero and the alert will skip them.
How quickly will I hear about a crashed Machine?
The alert checks Machine states every 5 minutes and compares them with the last check, so you hear about a change within a few minutes, and only once per change.
Will a stopped staging Machine stay stopped all night?
Not always. Fly Proxy may start it again if a request comes in, so if staging gets traffic overnight, expect it to wake up until the next scheduled stop.
Is AI needed for these Fly.io automations?
No. They compare states, dates and counts. For a written weekly summary, use the AI that is bundled with every ClickRuntime plan, no separate key required.
Is this a Fly.io connector for ChatGPT or Claude?
Not for chatting with Fly.io data. A chat connector lets your assistant read and change Fly.io 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 Fly.io event.

Related pages

Keep exploring

Tell your assistant what Fly.io should do

Free plan. No credit card.

Add to ChatGPTAdd to Claude