> For a complete page index, fetch https://docs.synthflow.ai/llms.txt. For full documentation content, fetch https://docs.synthflow.ai/llms-full.txt.

# Logs

> Access detailed logs for calls, chats, API requests, and webhook interactions in one centralized location.

![Logs page in the Synthflow dashboard](https://storage.googleapis.com/granular-changelog/doc-images/logs_0.png)

Synthflow provides a unified logging system that gives you complete visibility into all your agent operations. Open the **Logs** page in your Synthflow dashboard to access four log types in one centralized place:

* **[Call logs](#call-logs)**: Complete call history with transcripts and metadata
* **[Chat logs](#chat-logs)**: Conversation history for chat agents across API, widget, WhatsApp, and SMS
* **[API logs](#api-logs)**: Audit trail of all API requests triggered by your agents
* **[Webhook logs](#webhook-logs)**: Webhook interactions and delivery status

## Call logs

![Call details drawer with overview, transcript, and actions](https://storage.googleapis.com/granular-changelog/doc-images/logs_1.png)

Call logs give you full visibility into every call your agents handle. Beyond the dashboard, you can [export call logs to CSV](/export-call-data) for reporting or consume the same data programmatically through the [post-call webhook](/webhooks), which also documents the full list of statuses and end-call reasons.

Select any call to open the call details drawer. The **Copy** menu in its header copies the **Call ID**, the **Call URL**, or the full call data as **JSON**, ready to paste into a support ticket. The drawer has five tabs:

#### Overview

The **Overview** tab shows the same outcome data as the [post-call webhook](/webhooks), grouped into sections. Hover over **End Reason**, **Disconnect Reason**, **Voicemail**, or **Prompt Reuse** to see what the field means.

* **Summary**: What happened on the call. Only agents with a post-call webhook or an email action get a summary.
* **Call**:
  * **Status**: The call's [current state or outcome](/webhooks#call-status-options), such as Completed, Failed, or No Answer
  * **End Reason**: [Why the conversation ended](/webhooks#end-call-reason-options), such as a goodbye, voicemail, or the maximum duration
  * **Disconnect Reason**: Which side of the line hung up, as the carrier reports it: `Agent hang-up`, `Human hang-up`, or the carrier's own reason
  * **Voicemail**: `Detected`, `Not detected`, `Detected after call` (the post-call check caught voicemail the call missed), or `Overturned after call` (the post-call check found no voicemail where the call flagged one). Hidden when the call did not run voicemail detection.
  * **Date**, **Started**, **Ended**, and **Duration**
* **Transfer**: Each [transfer attempt](/transfer-outcome-states), its outcome, and how far into the call it started. Shown only on calls with a transfer.
* **Voicemail Message**: The message the agent left, when it left one.
* **Agent**: **Name**, **ID**, [**Version**](/version-control), and **Number**, the agent's phone number when the call used one.
* **Contact**: **Number**, **Name** (or `Unknown Contact`), and **Labels**.
* **Technical**: **Deployment** (such as Telephony), **Telephony Type** (such as Phone, Widget, or Web Call), [**Prompt Reuse**](/collect-analytics#prompt-reuse), and **Secondary Call ID** when the call has one.
* **Agents Used**: Every agent that handled the call, shown when more than one did.
* **Raw Data**: **Node & Stage Timings** (time spent in each node and stage) and **Original Payload** (the payload the call started with), as expandable JSON.

> **Note**
>
> The **Duration** shown in the call log reflects the total call duration, which includes all phases of the call such as PBX delay, ringing time, and conversation time. The **Recording**, however, only captures the conversation portion of the call. This means the recording duration will often be shorter than the total duration displayed in the log.
>
> For example, a call with a logged duration of 18 seconds may include a PBX delay (e.g., \~4 seconds), ringing (e.g., \~7 seconds), and actual conversation (e.g., \~7 seconds). In this case, the recording would only be 7 seconds long since it starts when the conversation begins.

#### Transcript

The **Recording** section plays the call's audio. Each warm transfer has its own recording in the **Actions** tab. Use the thumbs up or thumbs down buttons to rate the call and help fine-tune your agent.

The **Transcript** section shows the conversation in chronological order:

* **Call started** marker with the call's start timestamp
* Speaker-labeled turns with the agent name and `Customer`
* Timestamps on every turn
* Inline markers for [actions](/actions-overview) and [knowledge base](/knowledge-base) lookups

You can opt out of saving recordings, transcripts, and other sensitive data from the agent's [Security & Compliance](/security-and-compliance) settings.

#### Actions

The **Actions** tab lists everything that ran during the call, including [actions](/actions-overview) and [knowledge base](/knowledge-base) lookups. For each entry you typically see a name, timestamp, status, and expandable request/response details.

* **Action name**: The custom action or knowledge base operation (for example a search titled like your knowledge base)
* **Action ID**: Unique identifier for tracking (where shown)
* **Timestamp**: When the action ran
* **Duration**: How long the step took to return, shown as `850ms`, `1.2s`, or `5m 20s`. Use it to find the slow endpoint behind a long silence on the call.
* **Status**: Success or failure
* **Parameters / Request**: Inputs sent for that step
* **Response / Return value**: Data returned
  For action-related API traffic, jump to the matching entry in [API logs](#api-logs) using the Call ID link.

#### Variables

The **Variables** tab lists every [variable](/variables) the call used, with the value it had on that call. Variables are grouped by where the value came from:

* **System**: [System variables](/variables#system-variables) such as `call_id`, the phone numbers, and `agent_current_time`
* **Pre-call**: [Pre-call variables](/variables#pre-call-variables) passed in with `custom_variables`
* **Telephony headers**: SIP headers received with an inbound call. They are not repeated under **Pre-call**.
* **Collected**: [Collected variables](/variables#collected-variables) the agent gathered, with each variable's description
* **Custom actions**, **Bookings**, and **Call transfer**: One entry per action that ran, with its **Inputs** and **Outputs**. A call transfer's inputs include the SIP headers it sent.
* **Information extractor**: The values each extractor produced. Inputs do not appear.
* **Actions**: Any other action that ran with variables, such as a custom evaluation or an MCP tool. Custom evaluations show only the values they produced.

Enter text in **Filter by name or value** to find a variable. Select a variable's name to copy it, or the copy icon next to a value to copy the value. **Copy as JSON** copies every variable on the call at once, and selecting an action's name opens that action.

An action that ran with no inputs or outputs is not listed, and neither is a SIP header that was configured but never filled. Post-call SMS and email actions do not appear. Values an information extractor fills appear twice, under **Collected** and under **Information extractor**.

#### Telephony

The **Telephony** tab opens the [SIP call ladder](/sip-call-ladder), a visual diagram of the SIP signaling flow for the call. Use it to inspect message exchanges (INVITE, 200 OK, BYE), debug connectivity issues, and download the [PCAP file](/sip-call-ladder#downloading-pcap-files) for deeper analysis in Wireshark.

The tab also reports [call quality](/sip-call-ladder#call-quality) for the call: MOS, round-trip time, jitter, and packet loss. Start there when a caller reports choppy or delayed audio.

### Find a call by phone number

The **Phone Number** filter returns calls whose contact number matches the number you enter exactly. Enter the full number, including the country code. Partial numbers and numbers without a country code return no results.

### Action filter

![Action filter on Call Logs open on All Actions, with a submenu for each action type such as Real-Time Booking, Call Transfers, and Information Extractors](https://storage.googleapis.com/granular-changelog/doc-images/changelog_filter_logs_by_action.png)

The **Action** filter shows only the calls that ran a specific action. Select **Action**, point to an action type such as **Call Transfers**, and select the action, or search for it by name. Select **All Actions** to clear the filter. MCP connectors are not listed.

To start from the action instead, open **Actions**, open the action's menu, and select **View Call Logs**. **Call logs** opens with the filter already set to that action.

### Live call monitoring

![Listen in to a live call from Call logs](https://storage.googleapis.com/granular-changelog/doc-images/call_logs_listen_in.png)

While a call is in progress, you can listen in to the live conversation as it happens. Monitoring is silent: neither the agent nor the caller can hear you, so you can observe without affecting the call. Live monitoring is available only while the call's status is `in-progress`. Once the call leaves that state, review the recording and transcript from the call details drawer instead.

Open the **Logs** page, find the call with the `in-progress` status, and select **Listen in** to start monitoring.

## Chat logs

![Chat details drawer with overview, transcript, and actions](https://storage.googleapis.com/granular-changelog/doc-images/logs_5.png)

Chat logs give you full visibility into every chat conversation your agents handle. Conversations are recorded when end users interact with a [chat agent](/chat) over API, widget, WhatsApp, or SMS, and when you [test an agent with chat](/test-your-agent#chat) from the agent editor. You can also consume the same data programmatically through the [post-conversation webhook](/chat#post-conversation-webhook).

Click on any chat log to view detailed information in the chat details drawer, organized into three tabs:

#### Overview

The **Overview** page shows the chat's status, timing, and agent-related information:

* **Status**: The chat's [current state](/chat#post-conversation-webhook) (e.g. `In Progress`, `Completed`)
* **End reason**: [Why the conversation ended](/chat#post-conversation-webhook), when applicable (e.g. `completed`, `inactivity_timeout`)
* **Date**: Date the conversation started
* **Started**: Timestamp when the first message was sent
* **Ended**: Timestamp when the conversation ended
* **Duration**: Total elapsed time
* **Agent**: Name of the chat agent that handled the conversation
* **Agent ID**: Unique identifier of the agent
* **Agent Version**: [Version](/version-control) of the agent configuration used

#### Transcript

The **Transcript** section shows the conversation in chronological order:

* **Call Started** marker with the conversation's start timestamp
* Speaker-labeled turns with the agent name (for example, `AI Agent`) and `User`
* Timestamps on every turn
* A **Show events** toggle to display inline [actions](/actions-overview) and [knowledge base](/knowledge-base) events alongside messages

You can opt out of saving transcripts and other sensitive data from the agent's [Security & Compliance](/security-and-compliance) settings.

#### Actions

The **Actions** tab lists everything the chat agent ran during the conversation, including [actions](/actions-overview), [knowledge base](/knowledge-base) lookups, and variables collected.

For each entry you typically see a name, timestamp, status, and expandable request/response details.

## API logs

![API logs table with method, status, and call ID columns](https://storage.googleapis.com/granular-changelog/doc-images/logs_3.png)

API logs track every outbound API request your agents make during calls and chats, including [custom actions](/about-custom-actions#create-and-configure-a-custom-action) and other integrations. Each entry links back to the [Call logs](#call-logs) entry that triggered it.

Click on any API log to inspect the request and response, organized into two tabs:

#### Request

The **Details** block shows the agent and call context behind the request:

* **Agent**: Name of the agent that triggered the request
* **Agent ID**: Unique identifier of the agent
* **Agent Version**: [Version](/version-control) of the agent configuration used
* **Trace ID**: Correlation ID used to connect related logs across services. Share it with support when investigating issues.
* **Call ID**: Identifier of the phone call or session that triggered the request. Use it to jump to the matching entry in [Call logs](#call-logs).
* **Date**: Date the request was made
* **Started**: Timestamp when the request was issued
* **Finished**: Timestamp when the response was received
* **Time During Call**: Time elapsed in the call when the request fired

#### Response

The **Details** block summarizes response sizing and timing:

* **Headers Size**: Size of the response headers
* **Body Size**: Size of the response body
* **Total Response Size**: Combined size of headers and body
* **Time to First Byte (TTFB)**: Time from request to first byte of response
* **Total Duration**: Total time to complete the request

## Webhook logs

![Webhook logs table with delivery status and response time](https://storage.googleapis.com/granular-changelog/doc-images/logs_4.png)

Webhook logs track every webhook delivery to and from your workspace, including [inbound webhooks](/webhooks#inbound-webhook), [post-call webhooks](/webhooks#post-call-webhook), and custom integrations. For payload shapes and setup, see [Webhooks](/webhooks). Each entry links back to the [Call logs](#call-logs) entry that triggered it. Click on any webhook log to inspect the request and response, organized into two tabs:

#### Request

The **Details** block shows the agent, call context, and webhook category:

* **Agent**: Name of the agent that triggered the webhook
* **Agent ID**: Unique identifier of the agent
* **Agent Version**: [Version](/version-control) of the agent configuration used
* **Trace ID**: Correlation ID used to connect related logs across services. Share it with support when investigating issues.
* **Call ID**: Identifier of the phone call or session that triggered the webhook. Use it to jump to the matching entry in [Call logs](#call-logs).
* **Type**: Webhook category (e.g. `External`, `Inbound`, `Custom Action`)
* **Date**: Date the webhook was triggered
* **Started**: Timestamp when the request was issued
* **Finished**: Timestamp when the response was received
* **Duration**: Total time the webhook took to complete

#### Response

The **Details** block summarizes the response:

* **Status Code**: HTTP response status code received from the endpoint
* **Size**: Size of the response payload

## Best practices

* **Always filter by date range** when querying logs. Large log volumes are slower to load without a time filter.
* **Search by identifier** (Call ID, Action ID, Agent name) rather than freeform keywords for faster, more accurate results.
* **Export in chunks** by applying filters and date ranges before exporting, and run exports regularly if you need to keep records beyond your plan's retention window.
* **Review API and webhook logs proactively** for failed requests, unusual response times, recurring error patterns, and webhook delivery failures that may indicate endpoint or integration issues.

## API access

Call, API, and webhook logs are also available programmatically. See the [API reference](/api-reference/platform-api/webhook-logs/list-webhook-logs) for the full set of endpoints and parameters. Chat logs are not yet available via the API.

## FAQ

#### Where do I find logs for a specific agent?

From the **Logs** page, use the **Agents** filter to scope every log type (calls, chats, API, webhook) to a specific agent.

#### Why is the recording shorter than the call duration?

The **Duration** field includes PBX delay, ringing, and conversation time, while the recording only captures the conversation portion. A logged duration of 18 seconds can correspond to a 7-second recording if there were 4 seconds of PBX delay and 7 seconds of ringing.

#### Why does the phone number filter return no calls?

The [Phone Number filter](#find-a-call-by-phone-number) only matches the complete number. Enter it with the country code. Partial numbers and numbers without a country code return no results.

#### Can I listen to a call while it is happening?

Yes. While a call's status is `in-progress`, open it from [Call logs](#call-logs) and select **Listen in** to monitor the live conversation. Monitoring is silent, so neither the agent nor the caller can hear you. Once the call ends, review the recording and transcript from the call details drawer instead.

#### How do I trace a custom action that failed during a call?

Open the call from [Call logs](#call-logs), switch to the **Actions** tab to find the failed step, then jump to [API logs](#api-logs) using the linked Call ID to inspect the request, response, and retry history.

#### How long are logs retained?

Retention depends on your plan. Export logs regularly using the **Export** button (call logs) or the [API reference](/api-reference/platform-api/webhook-logs/list-webhook-logs) if you need historical records beyond your plan's retention window.