Gong: List Call Outcomes

List call outcomes (/v2/call-outcomes).

Tool ID: gong_list_call_outcomes

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_list_call_outcomes',
  {},
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute gong_list_call_outcomes --input '{}' --json

Example response

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

{
  "data": {
    "requestId": "request_123",
    "outcomes": [
      {
        "callOutcome": "example",
        "displayOrder": 123,
        "connectStatus": "CONNECTED"
      }
    ]
  }
}

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

Input reference

Use this endpoint to retrieve the list of available call outcomes defined in Gong. Call outcomes are used to categorize the result of a call (e.g., “Connected”, “No Answer”) and are set in the Dialer setup page. When accessed through a Bearer token authorization method, this endpoint requires the scope ‘api:call-outcomes:read’. This action does not require input fields.

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.outcomes`	`array`	No	—	The call outcomes of the company Items must be unique.
`result.data.outcomes[].callOutcome`	`string`	No	—	The call outcome name
`result.data.outcomes[].displayOrder`	`integer`	No	—	The display order when selecting a call outcome at the end of a call Format: `int32`.
`result.data.outcomes[].connectStatus`	`"CONNECTED" \| "NOT_CONNECTED"`	No	—	Indicates whether the call was connected or not. Possible values: Connected, Not connected Allowed: `CONNECTED`, `NOT_CONNECTED`.
`result.data.outcomes[].sentiment`	`"POSITIVE" \| "NEGATIVE" \| "NEUTRAL"`	No	—	The sentiment associated with the outcome (negative, positive, neutral) Allowed: `POSITIVE`, `NEGATIVE`, `NEUTRAL`.
`result.data.outcomes[].todoAction`	`"COMPLETE" \| "COMPLETE_AND_REMOVE"`	No	—	Specifies how to handle to-do items for the call when this outcome is selected. Allowed: `COMPLETE`, `COMPLETE_AND_REMOVE`.
`result.data.outcomes[].automation`	`"MARK_AS_OPT_OUT"`	No	—	Specifies the automation to run when this outcome is selected. Allowed: `MARK_AS_OPT_OUT`.
`result.data.outcomes[].category`	`"ANSWERED" \| "NOT_ANSWERED"`	No	—	The outcome category (example - answered vs not answered) Allowed: `ANSWERED`, `NOT_ANSWERED`.
`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: List Call Outcomes

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