ActionFly.ioUpdated September 2026
What Fly.io apps exist?
Short answer: You can list fly.io apps in Fly.io by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Fly.io List Fly.io Apps action to a workflow, map its 0 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Sample request
{}
Returns
{"apps": [{"id": "app123","name": "my-app","status": "running","organization": {"slug": "personal"}}]}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for List Fly.io Apps.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about List Fly.io Apps.
What does the List Fly.io Apps action do in Fly.io?
Returns every Fly app in the org with current state. Useful for inventory workflows or for "iterate every app and restart" mass-operation patterns.
What inputs does List Fly.io Apps require?
List Fly.io Apps has no required inputs. Sensible defaults are applied if you leave fields blank.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Fly.io returns an error?
The run history shows the failed step with its input and the error message Fly.io returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does List Fly.io Apps support batch operations?
Run List Fly.io Apps inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Fly.io's rate limits.
More actions