> ## 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 Call: Inputs, Cost & CLI Example

> Retrieve data for a specific call (/v2/calls/{id}). Includes inputs, outputs, pricing notes, Deepline CLI examples, and GTM automation guidance.

## 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_call:{"id":"{{id}}"}' --json
```

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

## Input Schema

| Name         | Type     | Required | Default | Description                                                      |
| ------------ | -------- | -------- | ------- | ---------------------------------------------------------------- |
| `payload.id` | `string` | Yes      |         | Gong's unique numeric identifier for the call (up to 20 digits). |

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

  ### Input JSON Schema

  ```json theme={null}
  {
    "type": "object",
    "description": "Retrieve data for a specific call. When accessed through a Bearer token authorization method, this endpoint requires the scope 'api:calls:read:basic'.",
    "properties": {
      "id": {
        "type": "string",
        "description": "Gong's unique numeric identifier for the call (up to 20 digits)."
      }
    },
    "required": [
      "id"
    ],
    "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."
          },
          "call": {
            "type": "object",
            "description": "call's metadata.",
            "properties": {
              "id": {
                "type": "string",
                "description": "Gong's unique numeric identifier for the call (up to 20 digits)."
              },
              "url": {
                "type": "string",
                "description": "The URL to the page in the Gong web application where the call is available."
              },
              "title": {
                "type": "string",
                "description": "The title of the call."
              },
              "scheduled": {
                "type": "string",
                "description": "Scheduled date and time of the call in the ISO-8601 format (e.g., '2018-02-18T02:30:00-07:00' or '2018-02-18T08:00:00Z', where Z stands for UTC).",
                "format": "date-time"
              },
              "started": {
                "type": "string",
                "description": "The date and time when the call was recorded in the ISO-8601 format (e.g., '2018-02-18T02:30:00-07:00' or '2018-02-18T08:00:00Z', where Z stands for UTC).",
                "format": "date-time"
              },
              "duration": {
                "type": "integer",
                "description": "The duration of the call, in seconds.",
                "format": "int64"
              },
              "primaryUserId": {
                "type": "string",
                "description": "The primary user ID of the team member who hosted the call."
              },
              "direction": {
                "type": "string",
                "description": "Call direction.",
                "enum": [
                  "Inbound",
                  "Outbound",
                  "Conference",
                  "Unknown"
                ]
              },
              "system": {
                "type": "string",
                "description": "The system with which the call was carried out (e.g., WebEx, ShoreTel, etc.)."
              },
              "scope": {
                "type": "string",
                "description": "The scope of the call: 'internal' if all the participants are from the company, 'external' if some participants are not from the company, or 'unknown' if the scope is unknown.",
                "enum": [
                  "Internal",
                  "External",
                  "Unknown"
                ]
              },
              "media": {
                "type": "string",
                "description": "Media type",
                "enum": [
                  "Video",
                  "Audio"
                ]
              },
              "language": {
                "type": "string",
                "description": "The language codes (as defined by ISO-639-2B). E.g., eng, fre, spa, ger, and ita. Also used are und (unsupported language), and zxx (not enough speech content for identification)."
              },
              "workspaceId": {
                "type": "string",
                "description": "Gong's unique numeric identifier for the call's workspace (up to 20 digits)."
              },
              "sdrDisposition": {
                "type": "string",
                "description": "The SDR disposition of the call. This can be an automated value provided by the provider, or manually entered by the rep."
              },
              "clientUniqueId": {
                "type": "string",
                "description": "The call's unique identifier in the origin recording system (typically a telephony recording system). The identifier is provided to Gong during the call creation via the Public API or through telephony systems integrations."
              },
              "customData": {
                "type": "string",
                "description": "Metadata as was provided to Gong during the call creation via the Public API."
              },
              "purpose": {
                "type": "string",
                "description": "The purpose of the call."
              },
              "meetingUrl": {
                "type": "string",
                "description": "The meeting provider URL on which the web conference was recorded."
              },
              "isPrivate": {
                "type": "boolean",
                "description": "If the call is private."
              },
              "calendarEventId": {
                "type": "string",
                "description": "The Id of the meeting in Google or Outlook Calendar."
              }
            },
            "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_call --payload '{
  "id": "string"
}' --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`.
