Fly.io

Deploy and manage apps, machines, and volumes on Fly.io edge infrastructure.

Detail	Value
Category	Cloud & Infra
Base URL	https://api.machines.dev/v1
Authentication	Bearer Token
Endpoints	8
Connector key	fly-io

Using Fly.io in a workflow

1. Go to Connections and click New Connection.
2. Pick Fly.io from the marketplace.
3. Enter your credentials (see Authentication above for what's expected).
4. In a workflow, drop an API Call node and select this connection.
5. Pick the operation you need from the Operation dropdown — the full list is below.

Available endpoints

Endpoint	Summary
GET /apps	List apps
POST /apps	Create an app
GET /apps/{app_name}	Get app details
GET /apps/{app_name}/machines	List machines
POST /apps/{app_name}/machines	Create a machine
POST /apps/{app_name}/machines/{machine_id}/start	Start a machine
POST /apps/{app_name}/machines/{machine_id}/stop	Stop a machine
GET /apps/{app_name}/volumes	List volumes

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET /apps

List apps

Detail	Value
Operation ID	cloud.listApps
Method	GET
Path	/apps

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Fly.io connection from the Connection dropdown.
3. In the Operation dropdown, select cloud.listApps.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Fly.io API reference.

POST /apps

Create an app

Detail	Value
Operation ID	cloud.createApp
Method	POST
Path	/apps

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Fly.io connection from the Connection dropdown.
3. In the Operation dropdown, select cloud.createApp.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Fly.io API reference.

GET /apps/{app_name}

Get app details

Detail	Value
Operation ID	cloud.getApp
Method	GET
Path	/apps/{app_name}

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Fly.io connection from the Connection dropdown.
3. In the Operation dropdown, select cloud.getApp.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Fly.io API reference.

GET /apps/{app_name}/machines

List machines

Detail	Value
Operation ID	cloud.listMachines
Method	GET
Path	/apps/{app_name}/machines

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Fly.io connection from the Connection dropdown.
3. In the Operation dropdown, select cloud.listMachines.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Fly.io API reference.

POST /apps/{app_name}/machines

Create a machine

Detail	Value
Operation ID	cloud.createMachine
Method	POST
Path	/apps/{app_name}/machines

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Fly.io connection from the Connection dropdown.
3. In the Operation dropdown, select cloud.createMachine.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Fly.io API reference.

POST /apps/{app_name}/machines/{machine_id}/start

Start a machine

Detail	Value
Operation ID	cloud.startMachine
Method	POST
Path	/apps/{app_name}/machines/{machine_id}/start

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Fly.io connection from the Connection dropdown.
3. In the Operation dropdown, select cloud.startMachine.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Fly.io API reference.

POST /apps/{app_name}/machines/{machine_id}/stop

Stop a machine

Detail	Value
Operation ID	cloud.stopMachine
Method	POST
Path	/apps/{app_name}/machines/{machine_id}/stop

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Fly.io connection from the Connection dropdown.
3. In the Operation dropdown, select cloud.stopMachine.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Fly.io API reference.

GET /apps/{app_name}/volumes

List volumes

Detail	Value
Operation ID	cloud.listVolumes
Method	GET
Path	/apps/{app_name}/volumes

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Fly.io connection from the Connection dropdown.
3. In the Operation dropdown, select cloud.listVolumes.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Fly.io API reference.