Gong: Get Request Status

Get Request Status (/v2/crm/request-status).

Tool ID: gong_get_request_status

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_get_request_status',
  {
    "integrationId": 123,
    "clientRequestId": "client_request_123"
  },
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute gong_get_request_status --input '{
  "integrationId": 123,
  "clientRequestId": "client_request_123"
}' --json

Example response

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

{
  "data": {
    "requestId": "request_123",
    "status": "PENDING",
    "errors": [
      {
        "line": 123,
        "description": "Example description"
      }
    ]
  }
}

Use deepline tools get 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

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).

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: Get Request Status

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