---
title: 'GET /apps/{app_name}/machines'
description: 'List machines'
---

# GET /apps/{app_name}/machines

List machines

| Detail | Value |
|---|---|
| Operation ID | `cloud.listMachines` |
| Method | `GET` |
| Path | `/apps/{app_name}/machines` |
| Connector | [Fly.io](./) |

## 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 <code v-pre>{{nodeId.data.path}}</code>. The exact response shape is documented on the upstream Fly.io API reference.