Inspect apps and machines or request a machine start or stop.
Explore 5 workflow actions for Fly.io, including account permissions and operation limits.
3 read actions2 write actions
WORKFLOW ACTIONS
What you can configure.
Choose an action in the workflow builder, connect an account, and map its inputs. These actions are available in the catalog; your account access and a successful test determine whether they work for your setup.
Get machine
Read
Read one machine's reported state and region.
Permissions and limits
Account permissions
Read the selected Fly machine
Operation limits
Returns machine identity and state only. Configuration, environment values, private addresses and event details are excluded.
List app machines
Read
Read state summaries for machines in one Fly app.
Permissions and limits
Account permissions
Read the selected Fly app
Operation limits
Returns machine identity and state only. Configuration, environment values, private addresses and event details are excluded.
Returns the provider's machine list without automatic pagination.
List organization apps
Read
Read app and machine counts for a named Fly organization.
Permissions and limits
Account permissions
Read apps in the named Fly organization
Operation limits
Uses the organization slug provided by the workflow. Fly authorizes that slug through the selected token.
Returns the provider's app list without automatic pagination.
Start machine
Write
Request that one stopped or suspended machine start.
Permissions and limits
Account permissions
Start the selected Fly machine
Operation limits
The response records the previous state, not a ready state. Read the machine afterward to confirm it started.
A lost response is uncertain and is never resent automatically.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Stop machine
Write
Request a graceful stop of one machine.
Permissions and limits
Account permissions
Stop the selected Fly machine
Operation limits
An `ok` response confirms Fly accepted the stop request. Read the machine afterward for its current state.
A lost response is uncertain and is never resent automatically.
A repeated request may repeat the external action. Review the previous result before retrying a write.
SETUP
Start with a controlled test.
01Connect the intended account
Use the account and permissions required for your process. Review the connection check before configuring a workflow action.
02Review inputs and access
Select a listed operation and map its required inputs. Use test records and add a human approval before writes that need review.
03Confirm the result
Inspect step outputs and confirm the result in Fly.io. A saved workflow is not a completed provider action.
Cloud & Infrastructure · CONNECTION
