Fly integration
Fly.io transforms containers into micro-VMs that run on hardware in 30+ regions…
- Provider
- fly
- Category
- Other
- Setup
- User-supplied API key
- Actions
- 45 listed in catalog
Start with one action
- Define the result. Choose one task, the data it needs, and who may run it. Start with a read when possible.
- Check access. Review the setup state below and the connection available to your workspace or app user. A catalog listing does not confirm that an account is connected.
- Inspect the current inputs. Ask the editor to discover the actions for Fly and inspect the selected action's required inputs and returned data before implementing it.
- Verify with test data. Compare the result with what you expected. Check unauthorized access and error handling before relying on the feature.
Developer details: the supplied app client
Generated apps that include src/lib/composio.ts expose the following import in their React app code:
import { executeAction } from "@/lib/composio";Its call signature is executeAction(actionName, params, options?). Supply the exact current action name and inputs from its specification. This import identifies the helper; it is not a complete or tested integration example.
The editor's os-list-integrations tool discovers an integration using integration_slug. Include both integration_slug and action_slug to retrieve the selected action's input and output schemas. Do not invent parameters from a catalog description.
executeAction requires a signed-in app user and any connection the action needs. The separate publicAction helper is only for a confirmed no-auth toolkit on an enabled public proxy. It does not make OAuth or API-key integrations anonymous.
Existing apps may contain an older client. Inspect the app's files and connection selection before changing a call. Keep provider credentials out of browser code and test failure handling; this guide does not promise automatic retries or synchronization.
Setup
This setup uses a supplied Fly API key. Follow the available connection form, then verify one action after setup.
Catalog actions
This saved catalog snapshot lists 45 actions. Names and inputs can change. Inspect the current action specification and connection requirements before adding a call; this list is not an execution test.
-
FLY_ADD_WIRE_GUARD_PEER -
FLY_CHECK_APP_NAME_AVAILABILITY -
FLY_CHECK_JOBS -
FLY_CHECK_USER_ONLY_TOKEN -
FLY_CREATE_CHECK_JOB -
FLY_CREATE_CHECK_JOB_RUN -
FLY_CREATE_DELEGATED_WIRE_GUARD_TOKEN -
FLY_CREATE_THIRD_PARTY_CONFIGURATION -
FLY_DELETE_DELEGATED_WIRE_GUARD_TOKEN -
FLY_DELETE_ORGANIZATION -
FLY_DELETE_REMOTE_BUILDER -
FLY_DELETE_THIRD_PARTY_CONFIGURATION
Show all 45 actions
-
FLY_DETACH_POSTGRES_CLUSTER -
FLY_ESTABLISH_SSH_KEY -
FLY_FETCH_NODES_BY_IDS -
FLY_GET_ADD_ON -
FLY_GET_ADD_ON_PROVIDER -
FLY_GET_APP_DETAILS -
FLY_GET_CERTIFICATE -
FLY_GET_CURRENT_TOKEN_INFO -
FLY_GET_LATEST_IMAGE_DETAILS -
FLY_GET_LATEST_IMAGE_TAG -
FLY_GET_MACHINE -
FLY_GET_NEAREST_REGION -
FLY_GET_NODE -
FLY_GET_ORGANIZATION -
FLY_GET_PERSONAL_ORGANIZATION -
FLY_GET_PLACEMENTS -
FLY_GET_PLATFORM_INFO -
FLY_GET_PRODUCTS -
FLY_GET_REGIONS -
FLY_GET_VIEWER_INFO -
FLY_ISSUE_CERTIFICATE -
FLY_LIST_ADD_ON_PLANS -
FLY_LIST_ADD_ONS -
FLY_LIST_APPS -
FLY_LIST_APPS_GRAPHQL -
FLY_LIST_CHECK_LOCATIONS -
FLY_LIST_MACHINES -
FLY_LIST_ORG_MACHINES -
FLY_REMOVE_WIRE_GUARD_PEER -
FLY_SET_APPS_V2_DEFAULT_ON -
FLY_UPDATE_THIRD_PARTY_CONFIGURATION -
FLY_VALIDATE_CONFIG -
FLY_VALIDATE_WIRE_GUARD_PEERS
Build with Fly
Describe one task you want your app to perform with Fly. Check the connection requirements, then verify the result in your app. Building and running the feature may use credits; review current pricing.