Gong: Get Flow Steps

Get flow details and steps for one or more Engage flows (/v2/flows/steps).

Tool ID: gong_get_flow_steps

Run this action

Use the TypeScript SDK for a single call. Put ctx.tools.execute(...) inside a Play when the call should be durable, scheduled, or run across a CSV.

import { Deepline } from 'deepline';

const deepline = await Deepline.connect();
const result = await deepline.tools.execute(
  'gong_get_flow_steps',
  {
    "flowIds": [
      "flow_123"
    ]
  },
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute gong_get_flow_steps --input '{
  "flowIds": [
    "flow_123"
  ]
}' --json

Example response

The SDK exposes this shape at result.toolResponse.raw. Values below are representative.

{
  "data": {
    "requestId": "request_123",
    "flows": [
      {
        "id": "id_123",
        "name": "Example",
        "folderId": "folder_123"
      }
    ]
  }
}

Use deepline tools get gong_get_flow_steps --json for the latest machine-readable contract.

Input reference

Request parameters for retrieving steps of one or more flows.

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

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`object`	Yes	—	Provider response payload.
`result.data.requestId`	`string`	No	—	A Gong request reference Id, generated for this request. Can be used for troubleshooting purposes.
`result.data.flows`	`array`	No	—	A list of flows with their steps
`result.data.flows[].id`	`string`	No	—	The id of the flow
`result.data.flows[].name`	`string`	No	—	The name of the flow
`result.data.flows[].folderId`	`string`	No	—	The id of the folder this flow is under
`result.data.flows[].visibility`	`"Company" \| "Personal" \| "Shared"`	No	—	The flow visibility type Allowed: `Company`, `Personal`, `Shared`.
`result.data.flows[].creationDate`	`string`	No	—	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).
`result.data.flows[].exclusive`	`boolean`	No	—	Indicates whether a prospect in this flow can be added to other flows
`result.data.flows[].description`	`string`	No	—	The description of the flow
`result.data.flows[].steps`	`array`	No	—	The list of steps for this flow
`result.data.flows[].steps[].id`	`string`	No	—	The unique identifier of the flow step
`result.data.flows[].steps[].stepOrder`	`integer`	No	—	The order of the step within the flow, starting from 1 Format: `int32`.
`result.data.flows[].steps[].action`	`"SEND_EMAIL" \| "AUTO_SEND_EMAIL" \| "CALL" \| "LINKEDIN_CONNECT" \| "LINKEDIN_MESSAGE" \| "CUSTOM"`	No	—	The type of action for this step (e.g. AUTO_SEND_EMAIL, CALL) Allowed: `SEND_EMAIL`, `AUTO_SEND_EMAIL`, `CALL`, `LINKEDIN_CONNECT`, `LINKEDIN_MESSAGE`, `CUSTOM`.
`result.data.flows[].steps[].subject`	`string`	No	—	The email subject for this step
`result.data.flows[].steps[].body`	`string`	No	—	The body content of this step
`result.data.flows[].steps[].isReply`	`boolean`	No	—	Whether this step is a reply to a previous email in the thread
`result.meta`	`object`	No	—	Additional response metadata (status, paging).

Deepline cost

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

Get started

Build and automate

Common workflows

Data and integrations

Reference

Gong: Get Flow Steps

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

​Run this action

​CLI

​Example response

​Input reference

​Output reference

​Deepline cost

​Related documentation

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

Related documentation