> ## Documentation Index
> Fetch the complete documentation index at: https://deepline.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Gong Get Flow Steps: Inputs, Cost & CLI Example

> Get flow details and steps for one or more Engage flows (/v2/flows/steps). Includes inputs, outputs, costs, and Deepline CLI examples for GTM automation.

## Run in Enrichment Spreadsheet

<Info>
  Use this function as a column step in `deepline enrich`.
</Info>

```bash theme={null}
deepline enrich --input leads.csv --output leads.enriched.csv --with 'result=gong_get_flow_steps:{}' --json
```

<Tip>
  Map payload values to spreadsheet columns with `{{column_name}}` placeholders.
</Tip>

## Input Schema

| Name              | Type    | Required | Default | Description                                                                     |
| ----------------- | ------- | -------- | ------- | ------------------------------------------------------------------------------- |
| `payload.flowIds` | `array` | No       |         | List of Engage Flow IDs to retrieve steps for. Maximum 20 flow IDs per request. |

<details>
  <summary>Show raw input schema</summary>

  ### Input JSON Schema

  ```json theme={null}
  {
    "type": "object",
    "description": "Request parameters for retrieving steps of one or more flows.",
    "properties": {
      "flowIds": {
        "type": "array",
        "description": "List of Engage Flow IDs to retrieve steps for. Maximum 20 flow IDs per request.",
        "items": {
          "type": "string",
          "description": "List of Engage Flow IDs to retrieve steps for. Maximum 20 flow IDs per request."
        }
      }
    },
    "required": [],
    "additionalProperties": false
  }
  ```
</details>

## Output Schema

| Name          | Type     | Required | Default | Description                                    |
| ------------- | -------- | -------- | ------- | ---------------------------------------------- |
| `result.data` | `object` | Yes      |         | Provider response payload.                     |
| `result.meta` | `object` | No       |         | Additional response metadata (status, paging). |

<details>
  <summary>Show raw output schema</summary>

  ### Output JSON Schema

  ```json theme={null}
  {
    "type": "object",
    "description": "Standard tool result payload.",
    "properties": {
      "data": {
        "type": "object",
        "description": "Provider response payload.",
        "properties": {
          "requestId": {
            "type": "string",
            "description": "A Gong request reference Id, generated for this request. Can be used for troubleshooting purposes."
          },
          "flows": {
            "type": "array",
            "description": "A list of flows with their steps",
            "items": {
              "type": "object",
              "description": "A list of flows with their steps",
              "properties": {
                "id": {
                  "type": "string",
                  "description": "The id of the flow"
                },
                "name": {
                  "type": "string",
                  "description": "The name of the flow"
                },
                "folderId": {
                  "type": "string",
                  "description": "The id of the folder this flow is under"
                },
                "visibility": {
                  "type": "string",
                  "description": "The flow visibility type",
                  "enum": [
                    "Company",
                    "Personal",
                    "Shared"
                  ]
                },
                "creationDate": {
                  "type": "string",
                  "description": "Creation time of the flow in ISO-8601 format (e.g., '2018-02-18T02:30:00-07:00' or '2018-02-18T08:00:00Z', where Z stands for UTC)."
                },
                "exclusive": {
                  "type": "boolean",
                  "description": "Indicates whether a prospect in this flow can be added to other flows"
                },
                "description": {
                  "type": "string",
                  "description": "The description of the flow"
                },
                "steps": {
                  "type": "array",
                  "description": "The list of steps for this flow",
                  "items": {
                    "type": "object",
                    "description": "The list of steps for this flow",
                    "properties": {
                      "id": {
                        "type": "string",
                        "description": "The unique identifier of the flow step"
                      },
                      "stepOrder": {
                        "type": "integer",
                        "description": "The order of the step within the flow, starting from 1",
                        "format": "int32"
                      },
                      "action": {
                        "type": "string",
                        "description": "The type of action for this step (e.g. AUTO_SEND_EMAIL, CALL)",
                        "enum": [
                          "SEND_EMAIL",
                          "AUTO_SEND_EMAIL",
                          "CALL",
                          "LINKEDIN_CONNECT",
                          "LINKEDIN_MESSAGE",
                          "CUSTOM"
                        ]
                      },
                      "subject": {
                        "type": "string",
                        "description": "The email subject for this step"
                      },
                      "body": {
                        "type": "string",
                        "description": "The body content of this step"
                      },
                      "isReply": {
                        "type": "boolean",
                        "description": "Whether this step is a reply to a previous email in the thread"
                      }
                    },
                    "additionalProperties": false
                  }
                }
              },
              "additionalProperties": false
            }
          }
        },
        "additionalProperties": false
      },
      "meta": {
        "type": "object",
        "description": "Additional response metadata (status, paging).",
        "additionalProperties": true
      }
    },
    "required": [
      "data"
    ],
    "additionalProperties": false
  }
  ```
</details>

## Advanced: Direct CLI

<Info>
  Use direct execution for single payload debugging.
</Info>

```bash theme={null}
deepline tools execute gong_get_flow_steps --payload '{}' --json
```

### CLI flags

| Flag                        | Description                                         |
| --------------------------- | --------------------------------------------------- |
| `--json`                    | Print machine-readable output.                      |
| `--wait`                    | Wait for terminal provider status when supported.   |
| `--debug`                   | Enable wait mode with additional status/log output. |
| `--wait-timeout SECONDS`    | Max seconds to wait in wait mode.                   |
| `--poll-interval SECONDS`   | Polling interval in seconds during wait mode.       |
| `--timeout SECONDS`         | Request timeout in seconds.                         |
| `--connect-timeout SECONDS` | Connection timeout in seconds.                      |

## Cost

* Pricing model: `fixed` (per call).
* Estimated Deepline credits: `0` per pricing unit.
* Provider-native pricing may still exist outside Deepline credit billing.
* Billing mode: `no_bill`.