Fly.io
Fly.io edge container deployments
Fly.io is the developer-friendly cloud for container-first applications — deploy a Docker container, Fly handles routing, edge replication, and global deployment to 30+ regions. Tiny Command exposes two read actions, no triggers (most Fly operations happen via the flyctl CLI; for orchestration via API, the GraphQL machine-management endpoints are reachable via HTTP action): Get Account Info (the authenticated account's details — name, plan, regions), List Apps (every Fly app in the org). The connection uses a Fly.io API token from fly.io/user/personal_access_tokens. Fly's positioning is "global-by-default" — apps run in multiple regions out of the box, with traffic routed to the nearest. Useful for latency-sensitive workloads. For workflows that interact with Fly programmatically (auto-scale based on metrics, restart unhealthy machines, deploy on a Git tag), the GraphQL API via HTTP action covers most needs; the typed actions here focus on read-side.
Do anything Fly.io can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| Get Fly.io Account Info | Returns the connected account's details — name, plan, available regions. The lookup for account inventory and capacity-planning workflows. |
| List Fly.io Apps | Returns every Fly app in the org with current state. Useful for inventory workflows or for "iterate every app and restart" mass-operation patterns. |
Pre-built Fly.io workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect Fly.io once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every Fly.io field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the Fly.io integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect Fly.io to Tiny Command?
What Fly.io triggers does Tiny Command support?
What Fly.io actions can I run from a workflow?
Is the Fly.io integration real-time?
Do I need to write code to use Fly.io with Tiny Command?
How much does the Fly.io integration cost?
More forms & surveys apps people connect.
Same category as Fly.io, ordered by how often teams pair them. Hover the carousel to pause.
Do more with Fly.io.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
