> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.meetgail.com/platform/workflows/node-reference/gail/get-call-data/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.meetgail.com/_mcp/server.

# Get Call Data

> Retrieves the recording, transcript, and details of a Gail call.

The Get Call Data node pulls everything Gail recorded about a call: the recording details,
the full transcript, who was on it, why they called, how it ended, and any custom fields.
Use it to process or route a workflow based on what actually happened on a call.

## When to use it

* You want to read the transcript of a call to decide what to do next.
* You want to route the run based on the call's category or how it ended.
* You want to hand the transcript to an [Agent](/platform/workflows/node-reference/ai/agent) to
  summarize or pull out key points.

## Inputs

| Field   | What it's for                                          | Example                                |
| ------- | ------------------------------------------------------ | -------------------------------------- |
| Call ID | The unique identifier of the call you want to look up. | `019e2b47-8c3a-7f56-b2d1-4a7e9c05d3f8` |

The Call ID can be a fixed value or an [expression](/platform/workflows/core-concepts/expressions/using-expressions-in-nodes)
that reads the ID from the trigger or an earlier step.

## Outputs

| Field        | What you get back                                                                                                        |
| ------------ | ------------------------------------------------------------------------------------------------------------------------ |
| Outcome      | Whether the call was found.                                                                                              |
| Call details | On success, the caller's name, the category and reason for the call, how it ended, any voicemail, and any custom fields. |
| Recording    | The recording's location and its length in seconds, when a recording is available.                                       |
| Transcript   | The turn-by-turn record of what was said.                                                                                |

Many fields can be empty depending on how far the call got, so treat anything you read
downstream as possibly missing.

## Example

After a renewal reminder call to Sarah Chen, a workflow uses Get Call Data to fetch the
transcript and category. A [Check](/platform/workflows/node-reference/logic-and-flow/check) step
then reads the category: if the call was about billing, the run routes to a follow-up
task; otherwise it hands the transcript to an [Agent](/platform/workflows/node-reference/ai/agent)
for a short summary logged against her record.

![The Get Call Data node configuration panel, showing the call identifier field.](/_fern-img/565b630fc2cd06989bf5fb1f4029cd71150f5457cb9a70cd6980a1de38f29f49.webp)

> **Note**
>
> Call details are only as complete as the call itself. A call that was short or went to
> voicemail may return little or no transcript, so check that a value is present before a
> later step depends on it.

## Related nodes

#### [Outbound Call](/platform/workflows/node-reference/gail/outbound-call)

Place the call whose data you want to read.

#### [Download Call Recording](/platform/workflows/node-reference/gail/download-call-recording)

Save the call's audio recording as a file.

#### [Check](/platform/workflows/node-reference/logic-and-flow/check)

Turn the call's category or outcome into a single labeled decision.

#### [Agent](/platform/workflows/node-reference/ai/agent)

Summarize the transcript or pull out key details.

> Documentation for Gail, the AI platform for financial services. Learn how to set up GailGPT and Gail Agent to automate customer communications for insurance, banking, and finance.