ActionFly.ioUpdated May 2026

What Fly.io apps exist?

Short answer: Drop the "Fly.io → List Fly.io Apps" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 2 Fly.io actions

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.

Google Sheets → Fly.io

2 Google Sheets triggers

HubSpot → Fly.io

18 HubSpot triggers

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 workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does List Fly.io Apps support batch operations?

Yes. Run List Fly.io Apps inside a Loop node to process arrays. Tiny Command handles Fly.io's rate limits automatically so you don't have to throttle manually.

More actions