ACTION_ID: gong_get_call_details
NAME: Gong: Get call details
CATEGORY: Outreach
CREDITS: 0

Fetch the metadata for one Gong call by ID — title, participants' host,
duration, direction, system, meeting URL and calendar linkage.

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

2. OUTPUTS

id (string) — Gong's unique numeric identifier for the call (up to 20
digits).

url (string) — The URL to the page in the Gong web application where the
call is available.

title (string) — The title of the call.

scheduled (date) — Scheduled date and time of the call in the ISO-8601
format.

started (date) — The date and time when the call was recorded in the
ISO-8601 format.

duration (number) — The duration of the call, in seconds.

primary_user_id (string) — The primary user ID of the team member who
hosted the call.

direction (string) — Call direction.

system (string) — The system with which the call was carried out (e.g.,
WebEx, ShoreTel, etc.).

scope (string) — The scope of the call.

media (string) — Media type.

language (string) — The language codes (as defined by ISO-639-2B).

workspace_id (string) — Gong's unique numeric identifier for the call's
workspace (up to 20 digits).

sdr_disposition (string) — The SDR disposition of the call.

client_unique_id (string) — The call's unique identifier in the origin
recording system.

custom_data (string) — Metadata as was provided to Gong during the call
creation via the Public API.

purpose (string) — The purpose of the call.

meeting_url (string) — The meeting provider URL on which the web
conference was recorded.

is_private (boolean) — If the call is private.

calendar_event_id (string) — The Id of the meeting in Google or Outlook
Calendar.

3. HOW TO CONFIGURE

Configure Action body:

{
  "inputs": {
    "call_id": "{{input.gong_call_id}}"
  }
}

Field-by-field:
  - call_id   Required. Gong's numeric call identifier (up to 20
              digits), passed as a string.

4. KEY NOTES

- This returns call metadata only. For the spoken content use
  `gong_get_call_transcript`.
- The Gong connection is required even though the action definition does
  not declare one — the worker resolves a `gong` connection at run time
  and fails the row without it.
- `call_id` must be a Gong call ID, not a calendar event ID or a meeting
  URL. `calendar_event_id` is returned as an output, not accepted as an
  input.
- An unknown call ID fails the row. Set
  `continue_workflow_if_action_fails` if the rest of the chain should
  still run.

5. WHERE IT FITS IN A WORKFLOW

Pattern: webhook or CRM import carrying call IDs ->
gong_get_call_details -> filter (duration greater than 300) ->
gong_get_call_transcript -> llm_models (summarise).

6. WHEN TO USE

Use gong_get_call_details to attach call metadata to a row — who hosted
it, how long it ran, whether it was inbound or outbound — before
deciding whether to pull the transcript.

7. WHEN NOT TO USE

Need what was actually said on the call
  -> action-detail/gong_get_call_transcript.txt

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

Last updated: 2026-08-03.