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

> Retrieve tracker details (/v2/settings/trackers). 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_list_trackers:{}' --json
```

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

## Input Schema

| Name                  | Type     | Required | Default | Description                                                                                                   |
| --------------------- | -------- | -------- | ------- | ------------------------------------------------------------------------------------------------------------- |
| `payload.workspaceId` | `string` | No       |         | The ID of the workspace the keyword trackers are in. When empty, all trackers in all workspaces are returned. |

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

  ### Input JSON Schema

  ```json theme={null}
  {
    "type": "object",
    "description": "Retrieves details of all keyword trackers in the system or in a given workspace. When accessed through a Bearer token authorization method, this endpoint requires the 'api:settings:trackers:read' scope.",
    "properties": {
      "workspaceId": {
        "type": "string",
        "description": "The ID of the workspace the keyword trackers are in. When empty, all trackers in all workspaces are returned."
      }
    },
    "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."
          },
          "keywordTrackers": {
            "type": "array",
            "description": "A list of keyword trackers.",
            "items": {
              "type": "object",
              "description": "The definition of a tracker.",
              "properties": {
                "trackerId": {
                  "type": "string",
                  "description": "The unique identifier of the tracker."
                },
                "trackerName": {
                  "type": "string",
                  "description": "The name of the tracker."
                },
                "workspaceId": {
                  "type": "string",
                  "description": "The id of the workspace the tracker is in."
                },
                "languageKeywords": {
                  "type": "array",
                  "description": "The words and phrases defined for the tracker. Each languagueKeywords object contains the words and phrases defined in the specified language.",
                  "items": {
                    "type": "object",
                    "description": "The tracker keywords definition.",
                    "properties": {
                      "language": {
                        "type": "string",
                        "description": "The ISO 639-2/B language code for the language the keywords are in. When set to \"mul\" (ISO 639-2/B code for multiple languages), the keywords are relevant for all languages."
                      },
                      "keywords": {
                        "type": "array",
                        "description": "A list of words and phrases in the specified language.",
                        "items": {
                          "type": "string"
                        }
                      },
                      "includeRelatedForms": {
                        "type": "boolean",
                        "description": "When true the tracker identifies words in different forms, for example, if the keyword is \"organize\", \"organized\" and \"organizes\" are also included."
                      }
                    },
                    "additionalProperties": false
                  }
                },
                "affiliation": {
                  "type": "string",
                  "description": "Sets whether to track the keywords when said by people affiliated to a specific company. Options are: \"Anyone\", \"Company\", \"NonCompany\"."
                },
                "partOfQuestion": {
                  "type": "boolean",
                  "description": "When true, only looks for the keywords when they are part of a question."
                },
                "saidAt": {
                  "type": "string",
                  "description": "Sets whether the words and phrases are tracked at the beginning, end or anytime in a call. Options are: \"Anytime\", \"First\", or \"Last\". For “First” and “Last” see the saidAtInterval and saidAtUnit fields to see how long to track the keywords for."
                },
                "saidAtInterval": {
                  "type": "integer",
                  "description": "Sets the period of time to check if the words or phrases came up in the call (according to the saidAt setting). This can be either minutes or percent depending on the value in the saidAtUnit parameter.",
                  "format": "int32"
                },
                "saidAtUnit": {
                  "type": "string",
                  "description": "Sets whether the time to look for keywords is in minutes or a percentage of the call duration (according to the saidAt setting)."
                },
                "saidInTopics": {
                  "type": "array",
                  "description": "Sets the topics in the call the tracker terms should be picked up in.",
                  "items": {
                    "type": "string"
                  }
                },
                "filterQuery": {
                  "type": "string",
                  "description": "A filter that defines which calls to include when searching for the keyword tracker. The filter is in JSON and is in the URL of the search page. Example: a filter for all outbound calls { \"type\": \"And\", \"filters\": [ { \"type\": \"CallDirection\", \"terms\": [\"OUTBOUND\"] } ] }"
                },
                "created": {
                  "type": "string",
                  "description": "Sets the date and time the tracker was created, in the ISO-8601 format, for example: '2024-01-17T16:20:05-03:00' or '2016-02-16T03:57:04.834+05:30' or '2020-11-20T21:30:07.233692Z', where Z stands for UTC."
                },
                "creatorUserId": {
                  "type": "string",
                  "description": "The Id of the team member who created the tracker. Null when the tracker is built-in."
                },
                "updated": {
                  "type": "string",
                  "description": "The date and time the tracker settings were last updated, in the ISO-8601 format, for example: '2024-01-17T16:20:05-03:00' or '2016-02-16T03:57:04.834+05:30' or '2020-11-20T21:30:07.233692Z', where Z stands for UTC."
                },
                "updaterUserId": {
                  "type": "string",
                  "description": "The Id of the team member who updated the tracker. Null when the tracker is built-in."
                }
              },
              "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_list_trackers --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`.
