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

> Get Request Status (/v2/crm/request-status). 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_request_status:{"integrationId":"{{integrationId}}","clientRequestId":"{{clientRequestId}}"}' --json
```

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

## Input Schema

| Name                      | Type      | Required | Default | Description                                                                          |
| ------------------------- | --------- | -------- | ------- | ------------------------------------------------------------------------------------ |
| `payload.integrationId`   | `integer` | Yes      |         | Integration ID generated when creating the integration                               |
| `payload.clientRequestId` | `string`  | Yes      |         | The client request ID used in the asynchronous endpoint you want to get a status for |

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

  ### Input JSON Schema

  ```json theme={null}
  {
    "type": "object",
    "description": ".public-api-info { background: rgb(222, 235, 255);}.public-api-tip { background: rgb(227, 252, 239);}.public-api-parameter { background: rgba(9,30,66,0.08);}.public-api-note { background: rgb(234, 230, 255);}.public-api-important { background: rgb(255, 250, 230);}.public-api-critical { background: rgb(255, 235, 230);}table, th, td { border: 1px solid gray; border-collapse: collapse;}th, td { padding: 5px;}th { text-align: left;}img { border: 2px solid #D3D5D9;} Returns the current status of the request for endpoints run asynchronously: POST /v2/crm/entities DELETE /v2/crm/integrations When accessed using a bearer token, this endpoint requires the 'api:crm:upload' scope. Status Codes PENDING: file is pending being processed IN_PROGRESS: file is being processed DONE: all objects in the file were successfully processed FAILED: failed to parse some objects, or a general error occurred when the file was being processed Correcting a file that failed to be processed: When the status in the response is FAILED do one of the following: If the response includes a list of errors, correct the errors in the file as follows: Using the errors.line attribute, locate and correct the data in the JSON file. You can resend the entire LDJSON file, or only the corrected records via the relevant API. Note: The response returns a maximum of 20 errors. To make sure you have corrected all errors, upload the entire file repeatedly until you receive a DONE status. A single error in the form of: {\"line\":0,\"description\":\".....\"} indicates a general processing error: Fix the LDJSON file according to the error message. Upload the entire LDJSON file again.",
    "properties": {
      "integrationId": {
        "type": "integer",
        "description": "Integration ID generated when creating the integration",
        "format": "int64"
      },
      "clientRequestId": {
        "type": "string",
        "description": "The client request ID used in the asynchronous endpoint you want to get a status for"
      }
    },
    "required": [
      "integrationId",
      "clientRequestId"
    ],
    "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."
          },
          "status": {
            "type": "string",
            "description": "Request status",
            "enum": [
              "PENDING",
              "IN_PROGRESS",
              "DONE",
              "FAILED"
            ]
          },
          "errors": {
            "type": "array",
            "items": {
              "type": "object",
              "properties": {
                "line": {
                  "type": "integer",
                  "description": "Line number of failed object",
                  "format": "int32"
                },
                "description": {
                  "type": "string",
                  "description": "Error description"
                }
              },
              "additionalProperties": false
            }
          },
          "totalErrorCount": {
            "type": "integer",
            "description": "Number of objects that failed parsing",
            "format": "int32"
          },
          "totalSuccessCount": {
            "type": "integer",
            "description": "Number of valid objects",
            "format": "int32"
          }
        },
        "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_request_status --payload '{
  "integrationId": "integer",
  "clientRequestId": "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`.