Connect Claude to Gong

List the calls recorded in a date range, with their ids, titles, times, durations and the Gong URL for each. This is the index: it is how you find the call ids that get_call_transcripts and get_call_details need. Both ends of the range are required - send them as ISO 8601 with an offset or a Z, e.g. "2026-08-01T00:00:00Z" - and the range is matched against each call's start time, with the upper bound exclusive. Ask for a narrow window; a busy Gong account records hundreds of calls a week.

Return everything Gong holds about specific calls short of the transcript itself: who was on them and in what role, the agenda structure, the topics discussed and how long each ran, the keyword trackers that fired, and - where the account's plan includes Gong's AI features - the brief, the outline, the key points and the call outcome. Takes call ids, from list_calls or search_calls. Every content flag is off unless you ask for it, so ask for what you will read: `include_content_brief` and `include_content_key_points` are the cheapest way to know what a call was about without pulling the transcript, and `include_media` returns audio and video URLs that need an extra scope and expire after eight hours. `context: "Extended"` adds the CRM records Gong matched the call to.

Return the transcripts of specific calls - the verbatim record of what each person said, split into sentences with a speaker id and start and end offsets in milliseconds. This is what the connector exists for, and it is the most sensitive thing it can return: a transcript is a real conversation with a customer who agreed to be recorded by Gong, so the payload is never written to the audit log. Give call ids from list_calls or search_calls, at most 100 at a time. Speaker ids match the party ids get_call_details returns, so call that alongside this when you need to know who was speaking rather than only what was said.

Find calls by date range, workspace or host rather than by id, and return a light record for each - who was on it and what it was about, without the topic and tracker detail get_call_details pulls. Use it when the question starts from a person or a period ("what did this rep run last week") rather than from a call you already have. Both ends of the range are required. It reaches the same endpoint as get_call_details and differs only in what it filters on and how much it asks for, which is why the two are separate operations: one takes call ids and returns everything, this one takes a window and returns enough to choose from.

List the Gong users in this account - the customer's own salespeople and managers, with their ids, names, email addresses, titles and which workspace each belongs to. A Gong user id is what search_calls filters hosts by and what get_daily_activity reports on. These are the caller's own colleagues rather than anybody they sell to, so the response stays in the audit log.

Fetch one Gong user by id - their name, email address, title, manager, workspace and settings. Use it to resolve a user id that appeared in a call record or an activity statistic into a colleague's name. Like list_users, this is the account's own staff directory.

List the workspaces in this Gong account, with their ids and names. A workspace is how a Gong account is divided - by region, by product line, by team - and its id is the filter every call operation here accepts. It takes no parameters and returns no call and no person, which is why it is the connection check: it proves the access key and secret are the right pair without reading anything about anybody.

List the keyword trackers the account has configured - the words and phrases Gong watches for in every call, such as a competitor's name or a pricing objection. This is the reference list behind the tracker counts get_call_details returns: without it a tracker id in a call record is a number with no meaning. Account configuration, not anybody's data.

Return day-by-day activity for the account's users: for each user and each day, the calls they ran and the emails they sent, listed individually. Bound it with plain dates rather than timestamps - `from_date` and `to_date` are calendar dates in the account's own time zone, which is different from every other operation here, and `to_date` is exclusive and may not be in the future. Narrow it to particular people with user_ids from list_users. The response is withheld from the audit log because it enumerates individual calls and emails, and a call title is usually a customer's name.