> ## 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 > Check whether a CRM data upload to a custom Gong CRM integration finished or failed. Includes inputs, outputs, SDK V2 examples, and Deepline cost. Check whether a CRM data upload to a custom Gong CRM integration finished or failed. > [!NOTE] > > Tool ID: `gong_get_request_status` ## Run this action Use the TypeScript SDK for one call. Use `ctx.tools.execute(...)` inside a Play for durable calls, scheduled calls, or CSV processing. ```ts theme={"languages":{"custom":["/languages/deepline-prompt.json"]}} import { Deepline } from 'deepline'; const deepline = await Deepline.connect(); const result = await deepline.tools.execute( 'gong_get_request_status', { "integrationId": 123, "clientRequestId": "client_request_123" }, ); console.log(result.toolResponse.raw); ``` ### CLI ```bash theme={"languages":{"custom":["/languages/deepline-prompt.json"]}} deepline tools execute gong_get_request_status --input '{ "integrationId": 123, "clientRequestId": "client_request_123" }' --json ``` ## Example response The SDK returns this shape at `result.toolResponse.raw`. The example values illustrate the response. ```json theme={"languages":{"custom":["/languages/deepline-prompt.json"]}} { "data": { "requestId": "request_123", "status": "PENDING", "errors": [ { "line": 123, "description": "Example description" } ] } } ``` Use `deepline describe gong_get_request_status --json` for the latest machine-readable contract. ## Input reference 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 See the live schema below for the complete notes. | Name | Type | Required | Default | Details | | - | - | - | - | - | | `payload.integrationId` | `integer` | Yes | — | Integration ID generated when creating the integration Format: `int64`. | | `payload.clientRequestId` | `string` | Yes | — | The client request ID used in the asynchronous endpoint you want to get a status for |
Show raw input schema ### Input JSON Schema ```json theme={"languages":{"custom":["/languages/deepline-prompt.json"]}} { "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 } ```
## 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.status` | `"PENDING" \| "IN_PROGRESS" \| "DONE" \| "FAILED"` | No | — | Request status Allowed: `PENDING`, `IN_PROGRESS`, `DONE`, `FAILED`. | | `result.data.errors` | `array` | No | — | — | | `result.data.errors[].line` | `integer` | No | — | Line number of failed object Format: `int32`. | | `result.data.errors[].description` | `string` | No | — | Error description | | `result.data.totalErrorCount` | `integer` | No | — | Number of objects that failed parsing Format: `int32`. | | `result.data.totalSuccessCount` | `integer` | No | — | Number of valid objects Format: `int32`. | | `result.meta` | `object` | No | — | Additional response metadata (status, paging). |
Show raw output schema ### Output JSON Schema ```json theme={"languages":{"custom":["/languages/deepline-prompt.json"]}} { "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 } ```
## Deepline cost * Pricing model: `fixed` (per call). * Estimated Deepline credits: `0` per pricing unit. * Provider-native pricing may still exist outside Deepline credit billing. ## Related documentation * [Gong provider guide](https://deepline.com/docs/providers/gong/guide.md) * [SDK V2 quickstart](https://deepline.com/docs/sdk-v2/quickstart.md) * [SDK reference](https://deepline.com/docs/sdk-v2/sdk-reference.md) * [Run tools across a CSV](https://deepline.com/docs/sdk-v2/batch-csv.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.