200 Gong calls and nobody has time to replay them. Your agent surfaces the exact objections, competitor mentions, and champion signals per deal, scoped to the rep who owns it.
Acts as the rep. Deal-level access and forecast attribution stay intact.
Credentials stay vaulted. AES-256, resolved at request time, never in context.
Scoped before every call. Rep permissions enforced. 90-day audit trail.
Tools your Gong agent reaches for, scoped per user.
CALL ANY TOOL
List a rep's calls, fetch a single call, pull a transcript, push an Engage flow. Same toolkit, every framework, no auth plumbing to maintain.
gong_calls_list
List calls
List Gong calls with optional filters for date range, workspace, and call IDs. Returns metadata including title, duration, participants, and direction.
Parameters
Name
Type
Required
Description
from_date_time
string
Optional
ISO 8601 start filter
to_date_time
string
Optional
ISO 8601 end filter
workspace_id
string
Optional
Gong workspace ID
cursor
string
Optional
Pagination cursor for next page
gong_calls_get
Get calls (extensive)
Retrieve enriched details for one or more calls by ID, participants, interaction stats, topics discussed, and CRM associations.
Parameters
Name
Type
Required
Description
call_ids
array
Required
Gong call IDs
from_date_time
string
Optional
ISO 8601 start filter
to_date_time
string
Optional
ISO 8601 end filter
gong_calls_transcript_get
Get call transcripts
Retrieve speaker-attributed, sentence-level transcripts with timing offsets for one or more calls.
Parameters
Name
Type
Required
Description
call_ids
array
Required
Gong call IDs to fetch transcripts for
from_date_time
string
Optional
ISO 8601 start filter
to_date_time
string
Optional
ISO 8601 end filter
gong_engage_tasks_list
List Engage tasks
List Gong Engage tasks for a user, call tasks, email tasks, LinkedIn tasks, and other follow-up actions.
Parameters
Name
Type
Required
Description
assignee_email
string
Required
Email of the user
from_date
string
Optional
ISO 8601 start date
to_date
string
Optional
ISO 8601 end date
gong_engage_flows_list
List Engage flows
List all Engage flows available to a user, including company, personal, and shared flows.
Parameters
Name
Type
Required
Description
flow_owner_email
string
Required
Rep email to scope available flows
workspace_id
string
Optional
Gong workspace ID
gong_engage_prospects_assign
Assign prospects to flow
Assign up to 200 CRM prospects (contacts or leads) to a specific Gong Engage flow.
Parameters
Name
Type
Required
Description
crm_prospect_ids
array
Required
CRM contact/lead IDs
flow_id
string
Required
ID of the Engage flow to enrol into
flow_instance_owner_email
string
Required
Rep email who owns the flow instance
gong_engage_task_complete
Complete Engage task
Mark a specific Gong Engage task as completed.
Parameters
Name
Type
Required
Description
task_id
string
Required
Gong Engage task ID to mark complete
completion_notes
string
Optional
Optional notes on task completion
gong_stats_interaction
Get interaction statistics
Get aggregated interaction stats, talk ratio, longest monologue, patience, question rate, across calls in a date range.
Parameters
Name
Type
Required
Description
from_date_time
string
Required
ISO 8601 start filter
to_date_time
string
Required
ISO 8601 end filter
call_ids
array
Optional
Limit stats to these specific calls
gong_scorecards_list
List scorecards
List all scorecard definitions, names, questions, and criteria used for call review and coaching.
Parameters
Name
Type
Required
Description
—
No parameters required
gong_coaching_get
Get coaching data
Get coaching sessions and manager feedback provided to team members.
Parameters
Name
Type
Required
Description
—
No parameters required
gong_users_list
List users
List all users in the Gong account with profiles, titles, and manager info.
Parameters
Name
Type
Required
Description
—
No parameters required
gong_trackers_list
List trackers
List all keyword tracker settings, tracked phrases and categories used to monitor conversation topics.
Parameters
Name
Type
Required
Description
—
No parameters required
Build your Agent
Drop the toolkit in, point it at the rep, and your agent can read Gong calls, transcripts, and coaching data from the first run.
const sk = new ScalekitClient(envUrl, clientId, clientSecret);
// list gong tools scoped to a specific user const { tools } = await sk.tools.listScopedTools("user_123", { filter: { connectionNames: ["gong"], toolNames: ["gong_calls_list", "gong_calls_get", "gong_transcript_get"] }, pageSize: 100, });
// wrap each Scalekit tool as a LangChain DynamicStructuredTool const lcTools = tools.map((t) => new DynamicStructuredTool({ name: t.tool.definition.name, description: t.tool.definition.description, schema: t.tool.definition.input_schema, func: async (args) => sk.tools.executeTool({ toolName: t.tool.definition.name, identifier: "user_123", toolInput: args, }), }));
These are the questions sales leaders ask Gong every week. Copy any prompt, paste into your agent, watch it route to the right tool with the rep's scope.
Secure your agent's access. Connectors ship in minutes
Other agent connector libraries treat auth as a demo afterthought. Scalekit starts with rep identity, scope enforcement, and audit so production deploys hold up.
01.
Bot calls break rep-level analytics
A shared Gong token looks fine in a demo. In production, every call retrieved looks like it came from a service account. Audit logs break. Per-rep scoping breaks. Scalekit resolves the credential of the actual user who triggered the agent, never a shared bot.
Storing a token is table stakes. The production question is different: is this agent, calling this tool, for this tenant, in this scope, permitted? Scalekit enforces that check before the API call, not inside a prompt.
// authn only has_token? yes call → 200 (anything)
Each customer's Gong credentials need real isolation. Per-tenant namespacing, scope configuration, and revocation can't be bolted on after the fact. Scalekit makes them the default.
Gong today. HubSpot, Salesforce tomorrow. Each new OAuth flow is maintenance burden. With Scalekit, every connector inherits the same vault, audit chain, and delegation pattern. Zero new auth code per connector.
// DIY: N tools × M tenants gong_oauth.py salesforce_oauth.py slack_oauth.py github_oauth.py … ×100
“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”