Platform engineers and operations teams using Fly.io Machines API manage apps, machines and persistent volumes as part of regular deployment work. A new machine or volume can matter to people outside the terminal, especially when a release or infrastructure change needs prompt attention.

Fly.io’s New Machine trigger can start Mobile Message’s Send SMS action with the app or machine information available in the event. New Volume can do the same for storage changes. You can also create a Mobile Message contact or add an operator to a list when an infrastructure event needs a defined notification group. This gives a team a direct alert without requiring someone to monitor every Fly.io dashboard change.

The Fly.io actions are available when a Mobile Message event starts a Zap. For example, an inbound SMS could trigger Create Machine, Start Machine or Update Machine if the required identifiers and configuration fields are supplied. Such workflows should be restricted and tested carefully because infrastructure actions can affect running services. This is a set of targeted automations, not an automatic control loop.