ACTION_ID: gong_get_call_transcript
NAME: Gong: Retrieve call transcript
CATEGORY: Outreach
CREDITS: 0

Retrieve the transcript of a Gong call as a list of monologues,
optionally scoped by date range and workspace.

PREREQUISITE: Gong account connection — the user must create it in the Floqer UI
(Connections page); an agent cannot. Without it the action fails the row with
a connection / authentication error. Confirm it exists before configuring.

1. INPUTS

call_id (string, required)
  Call ID. Call Id to be filtered

from_date (date, optional)
  From Date. Date and time from which to list recorded calls. Format:
  '2018-02-18'

to_date (date, optional)
  To Date. Date and time until which to list recorded calls. Format:
  '2018-02-18'

workspace_id (string, optional)
  Workspace ID. Workspace Identifier

2. OUTPUTS

call_id (string) — Gong's unique numeric identifier for the call.

call_transcript (raw_array) — List of monologues.

3. HOW TO CONFIGURE

Configure Action body:

{
  "inputs": {
    "call_id": "{{input.gong_call_id}}",
    "from_date": "2026-07-01",
    "to_date": "2026-08-01"
  }
}

Field-by-field:
  - call_id       Required. Gong's numeric call identifier.
  - from_date /   Optional `YYYY-MM-DD` bounds. Narrow the window when
    to_date       the call ID is ambiguous across workspaces.
  - workspace_id  Optional. Needed only on multi-workspace Gong
                  accounts.

4. KEY NOTES

- `call_transcript` is a `raw_array` of monologue objects, not a flat
  string. Feed it to an LLM by stringifying it in a `formula` first, or
  reference the whole array in a prompt.
- The Gong connection is required even though the action definition does
  not declare one.
- Gong only exposes transcripts for calls it has finished processing. A
  call fetched too soon after it ends returns nothing.
- Dates are `YYYY-MM-DD`; a full ISO timestamp is rejected.

5. WHERE IT FITS IN A WORKFLOW

Pattern: gong_get_call_details -> gong_get_call_transcript -> llm_models
(extract objections / next steps) -> hubspot_update_object.

6. WHEN TO USE

Use gong_get_call_transcript to bring call content into a workflow for
LLM summarisation, objection extraction or CRM enrichment.

7. WHEN NOT TO USE

Only need call metadata
  -> action-detail/gong_get_call_details.txt

The meetings are recorded in Fireflies
  -> action-detail/get_fireflies_meeting_transcription.txt

Last updated: 2026-08-03.