Can I use Gong as a CLI?

Yes. KosmoKrator exposes a Gong CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Gong through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Gong tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Gong credentials stored?

Gong credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Gong MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

communication

Gong CLI for AI Agents

Use the Gong CLI from KosmoKrator to call Gong tools headlessly, return JSON, inspect schemas, and automate workflows from coding agents, scripts, and CI.

8 functions 8 read 0 write API key auth

Submit Gong feedback View package source

Gong CLI Setup

Gong can be configured headlessly with `kosmokrator integrations:configure gong`.

# Install KosmoKrator first if it is not available on PATH.
curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash

# Configure and verify this integration.
kosmokrator integrations:configure gong --set access_key="$GONG_ACCESS_KEY" --set access_key_secret="$GONG_ACCESS_KEY_SECRET" --enable --read allow --write ask --json
kosmokrator integrations:doctor gong --json
kosmokrator integrations:status --json

Credentials

Authentication type: API key api_key. Configure credentials once, then use the same stored profile from scripts, coding CLIs, Lua code mode, and the MCP gateway.

Key	Env var	Type	Required	Label
`access_key`	`GONG_ACCESS_KEY`	Secret `secret`	yes	Access Key
`access_key_secret`	`GONG_ACCESS_KEY_SECRET`	Secret `secret`	yes	Access Key Secret
`url`	`GONG_URL`	URL `url`	no	Gong API URL

Call Gong Headlessly

Use the generic call form when another coding CLI or script needs a stable universal interface.

kosmo integrations:call gong.gong_list_calls '{
  "fromDateTime": "example_fromDateTime",
  "toDateTime": "example_toDateTime",
  "workspaceId": "example_workspaceId",
  "userId": "example_userId",
  "cursor": "example_cursor",
  "limit": 1
}' --json

Use the provider shortcut form for shorter human-facing commands.

kosmo integrations:gong gong_list_calls '{
  "fromDateTime": "example_fromDateTime",
  "toDateTime": "example_toDateTime",
  "workspaceId": "example_workspaceId",
  "userId": "example_userId",
  "cursor": "example_cursor",
  "limit": 1
}' --json

Agent Discovery Commands

These commands return structured output for coding agents that need to inspect capabilities before choosing a function.

kosmo integrations:docs gong --json
kosmo integrations:docs gong.gong_list_calls --json
kosmo integrations:schema gong.gong_list_calls --json
kosmo integrations:search "Gong" --json
kosmo integrations:list --json

All CLI Functions

Every function below can be called headlessly. The generic form is stable across all integrations; the provider shortcut is shorter but specific to Gong.

`gong.gong_list_calls`

Read read

List call recordings from Gong. Filter by date range, participants, or other criteria. Returns call metadata including title, duration, participants, and timestamps.

Parameters: fromDateTime, toDateTime, workspaceId, userId, cursor, limit

Generic CLI call

kosmo integrations:call gong.gong_list_calls '{"fromDateTime":"example_fromDateTime","toDateTime":"example_toDateTime","workspaceId":"example_workspaceId","userId":"example_userId","cursor":"example_cursor","limit":1}' --json

Provider shortcut

kosmo integrations:gong gong_list_calls '{"fromDateTime":"example_fromDateTime","toDateTime":"example_toDateTime","workspaceId":"example_workspaceId","userId":"example_userId","cursor":"example_cursor","limit":1}' --json

`gong.gong_get_call`

Read read

Get detailed information about a specific call in Gong, including metadata, participants, and tracking data.

Parameters: callId

Generic CLI call

kosmo integrations:call gong.gong_get_call '{"callId":"example_callId"}' --json

Provider shortcut

kosmo integrations:gong gong_get_call '{"callId":"example_callId"}' --json

`gong.gong_list_transcripts`

Read read

List call transcripts from Gong. Filter by download date, call type, or status. Returns transcript metadata including call ID, language, and processing status.

Parameters: page, limit, download_date, call_type, status

Generic CLI call

kosmo integrations:call gong.gong_list_transcripts '{"page":1,"limit":1,"download_date":"example_download_date","call_type":"example_call_type","status":"example_status"}' --json

Provider shortcut

kosmo integrations:gong gong_list_transcripts '{"page":1,"limit":1,"download_date":"example_download_date","call_type":"example_call_type","status":"example_status"}' --json

`gong.gong_get_transcript`

Read read

Get the full transcript of a specific call in Gong, including speaker turns, timestamps, and transcript metadata.

Parameters: transcript_id

Generic CLI call

kosmo integrations:call gong.gong_get_transcript '{"transcript_id":"example_transcript_id"}' --json

Provider shortcut

kosmo integrations:gong gong_get_transcript '{"transcript_id":"example_transcript_id"}' --json

`gong.gong_list_users`

Read read

List users in the Gong workspace. Returns user details including name, email, title, and manager.

Parameters: cursor, limit

Generic CLI call

kosmo integrations:call gong.gong_list_users '{"cursor":"example_cursor","limit":1}' --json

Provider shortcut

kosmo integrations:gong gong_list_users '{"cursor":"example_cursor","limit":1}' --json

`gong.gong_list_deals`

Read read

List deals tracked in Gong. Filter by date range or pipeline stage. Returns deal metadata including name, stage, amount, and associated users.

Parameters: fromDateTime, toDateTime, pipelineId, stageIds, cursor, limit

Generic CLI call

kosmo integrations:call gong.gong_list_deals '{"fromDateTime":"example_fromDateTime","toDateTime":"example_toDateTime","pipelineId":"example_pipelineId","stageIds":"example_stageIds","cursor":"example_cursor","limit":1}' --json

Provider shortcut

kosmo integrations:gong gong_list_deals '{"fromDateTime":"example_fromDateTime","toDateTime":"example_toDateTime","pipelineId":"example_pipelineId","stageIds":"example_stageIds","cursor":"example_cursor","limit":1}' --json

`gong.gong_list_interactions`

Read read

List customer interactions tracked in Gong. Filter by date range, activity type, or participants. Returns interaction metadata including type, duration, and parties involved.

Parameters: fromDateTime, toDateTime, activityTypes, cursor, limit

Generic CLI call

kosmo integrations:call gong.gong_list_interactions '{"fromDateTime":"example_fromDateTime","toDateTime":"example_toDateTime","activityTypes":"example_activityTypes","cursor":"example_cursor","limit":1}' --json

Provider shortcut

kosmo integrations:gong gong_list_interactions '{"fromDateTime":"example_fromDateTime","toDateTime":"example_toDateTime","activityTypes":"example_activityTypes","cursor":"example_cursor","limit":1}' --json

`gong.gong_get_current_user`

Read read

Get the currently authenticated Gong user profile. Useful for verifying credentials and understanding whose data is being accessed.

Parameters: none

Generic CLI call

kosmo integrations:call gong.gong_get_current_user '{}' --json

Provider shortcut

kosmo integrations:gong gong_get_current_user '{}' --json

Function Schemas

Use these parameter tables when building CLI payloads without calling integrations:schema first.

`gong.gong_list_calls`

List call recordings from Gong. Filter by date range, participants, or other criteria. Returns call metadata including title, duration, participants, and timestamps.

Operation: Read read
Schema command: kosmo integrations:schema gong.gong_list_calls --json

Parameter	Type	Required	Description
`fromDateTime`	string	no	Start of date range in ISO 8601 format (e.g., "2025-01-01T00:00:00Z").
`toDateTime`	string	no	End of date range in ISO 8601 format (e.g., "2025-01-31T23:59:59Z").
`workspaceId`	string	no	Workspace ID to filter calls by.
`userId`	array	no	Array of user IDs to filter calls by.
`cursor`	string	no	Cursor for pagination — pass the value from a previous response to get the next page.
`limit`	integer	no	Maximum number of calls to return (default: 100).

`gong.gong_get_call`

Get detailed information about a specific call in Gong, including metadata, participants, and tracking data.

Operation: Read read
Schema command: kosmo integrations:schema gong.gong_get_call --json

Parameter	Type	Required	Description
`callId`	string	yes	The unique call identifier.

`gong.gong_list_transcripts`

List call transcripts from Gong. Filter by download date, call type, or status. Returns transcript metadata including call ID, language, and processing status.

Operation: Read read
Schema command: kosmo integrations:schema gong.gong_list_transcripts --json

Parameter	Type	Required	Description
`page`	integer	no	Page number for pagination (starting from 1).
`limit`	integer	no	Maximum number of transcripts to return per page.
`download_date`	string	no	Filter transcripts by download date in ISO 8601 format (e.g., "2025-01-15").
`call_type`	string	no	Filter by call type (e.g., "conference", "webinar", "phone").
`status`	string	no	Filter by transcript processing status (e.g., "completed", "processing", "failed").

`gong.gong_get_transcript`

Get the full transcript of a specific call in Gong, including speaker turns, timestamps, and transcript metadata.

Operation: Read read
Schema command: kosmo integrations:schema gong.gong_get_transcript --json

Parameter	Type	Required	Description
`transcript_id`	string	yes	The unique transcript identifier.

`gong.gong_list_users`

List users in the Gong workspace. Returns user details including name, email, title, and manager.

Operation: Read read
Schema command: kosmo integrations:schema gong.gong_list_users --json

Parameter	Type	Required	Description
`cursor`	string	no	Cursor for pagination — pass the value from a previous response to get the next page.
`limit`	integer	no	Maximum number of users to return (default: 100).

`gong.gong_list_deals`

List deals tracked in Gong. Filter by date range or pipeline stage. Returns deal metadata including name, stage, amount, and associated users.

Operation: Read read
Schema command: kosmo integrations:schema gong.gong_list_deals --json

Parameter	Type	Required	Description
`fromDateTime`	string	no	Start of date range in ISO 8601 format (e.g., "2025-01-01T00:00:00Z").
`toDateTime`	string	no	End of date range in ISO 8601 format (e.g., "2025-01-31T23:59:59Z").
`pipelineId`	string	no	Pipeline ID to filter deals by.
`stageIds`	array	no	Array of stage IDs to filter deals by.
`cursor`	string	no	Cursor for pagination — pass the value from a previous response to get the next page.
`limit`	integer	no	Maximum number of deals to return (default: 100).

`gong.gong_list_interactions`

List customer interactions tracked in Gong. Filter by date range, activity type, or participants. Returns interaction metadata including type, duration, and parties involved.

Operation: Read read
Schema command: kosmo integrations:schema gong.gong_list_interactions --json

Parameter	Type	Required	Description
`fromDateTime`	string	no	Start of date range in ISO 8601 format (e.g., "2025-01-01T00:00:00Z").
`toDateTime`	string	no	End of date range in ISO 8601 format (e.g., "2025-01-31T23:59:59Z").
`activityTypes`	array	no	Array of activity types to filter by (e.g., ["call", "email", "meeting"]).
`cursor`	string	no	Cursor for pagination — pass the value from a previous response to get the next page.
`limit`	integer	no	Maximum number of interactions to return (default: 100).

`gong.gong_get_current_user`

Get the currently authenticated Gong user profile. Useful for verifying credentials and understanding whose data is being accessed.

Operation: Read read
Schema command: kosmo integrations:schema gong.gong_get_current_user --json

Parameter	Type	Required	Description
No parameters.

Permissions

Headless calls still follow the integration read/write permission policy. Configure read/write defaults with integrations:configure. Add --force only for trusted automation that should bypass that policy.