Fly.io deploy and downtime notifications on your phone

Fly.io has no webhooks for an app's deploys or machines; here is what works instead: a line after fly deploy, the GitHub Action, and a watch on the app's health URL.

Fly.io's own page was read on 12 September 2026 for every step below. If a menu has moved since, write to hello@youlmk.com and it is corrected the same day.

What Fly.io sends

Nothing on its own. Fly.io's staff on its forum: the platform does not offer deployment notifications (29 November 2022), and machine-state webhooks exist only for the Extensions Program (9 January 2025); both read on 12 September 2026.

What arrives in the inbox

What works instead

1. After fly deploy in your script or CI: curl -s youlmk.com/w/<your key> -d '{"title": "api deployed"}' when it succeeds, and a high-priority one when it fails (the cron guide shows the shape).
2. If you deploy from GitHub Actions, add the YouLMK notify action as the last step, with if: failure() for the failures.
3. For downtime, a YouLMK watch: "tell me when my-app.fly.dev/health stops returning 200", checked every minute.

Make it quiet where it should be

Everything above lands with the source's own rules: its Reach (Silent, Badge, Banner, Break through), whether quiet hours hold it, and grouping of repeats into one card. Set them once on the source, in the app or at app.youlmk.com; the service never has to change. Unknown fields arrive as rows on the card, up to six; the whole request is capped at 8 KB (Webhooks).

Try it

The trial is 10 notifications and 3 watches, no card. Get your key, or read the webhooks reference first.

Source

community.fly.io, deploy notifications (2022) and webhooks for machine states (2025), read 12 September 2026.