Zendesk Talk

Zendesk Talk is the built-in voice solution inside Zendesk Support, letting your team handle inbound and outbound calls, manage IVR menus, and track agent performance — all within the Zendesk ecosystem. Connecting it to Coupler.io lets you pull call records, agent activity, queue status, and phone configuration data into your analytics tools.

Why connect Zendesk Talk to Coupler.io?

• Export call logs, agent activity, and queue metrics to Google Sheets, Excel, BigQuery, or Looker Studio for custom reporting

• Combine Zendesk Talk data with other sources (like Zendesk Support tickets) using Join or Append transformations

• Send call summaries and agent performance data to AI tools like ChatGPT, Claude, or Gemini for automated analysis

• Keep a historical record of call data outside Zendesk Talk's own retention limits

Prerequisites

• A Zendesk account with Talk enabled

• Your Zendesk subdomain (e.g., yourcompany.zendesk.com)

• A Zendesk API token — generate one in Admin Center → Apps and integrations → Zendesk API → API tokens

• Your Zendesk agent email address (used alongside the API token)

Quick start

Start with the Calls or Agents activities entity — these give you the most actionable data right away.

How to connect

1

Create a new data flow. In Coupler.io, click Add data flow, then search for and select Zendesk Talk as your source.

2

Enter your credentials. Provide your Zendesk subdomain, your agent email address, and your API token. Coupler.io uses these to authenticate with the Zendesk Talk API.

3

Select an entity. Choose the data you want to export — for example, Calls, Agents activities, or Current queue activities. If you selected Calls or Call legs, use the date picker to set a start date for the export.

4

Choose a destination. Select where you want your data to go — Google Sheets, Excel, BigQuery, Looker Studio, or an AI destination like ChatGPT or Claude.

5

Run the data flow. Click Run to execute a manual sync. Once it completes successfully, your data will appear in the destination you chose.

Available entities

Entity	Description
Calls	Complete call records with duration, participants, and outcomes
Call legs	Individual segments of calls with detailed routing info
Agents activities	Activity metrics and stats per agent
Agents overviews	Summary of all agents' performance and status
Account overviews	High-level account statistics and usage metrics
Current queue activities	Real-time call queue status
Phone numbers	Phone numbers configured in your account
Addresses	Phone number addresses and their configurations
IVRs	IVR systems and their configurations
IVR menus	Menu options within IVR systems
IVR routes	Call routing rules configured in IVR systems
Greetings	Voice greetings used in call flows
Greeting categories	Categories used to organize greetings

Zendesk Talk data overview

Zendesk Talk exposes data across three broad areas: call activity (individual calls and call segments), agent performance (real-time and historical metrics per agent), and phone configuration (IVRs, phone numbers, greetings, and routing). Here's a breakdown of what each entity contains.

Entities at a glance

Entity	What it contains
Calls	Full call records — duration, direction, status, assigned agent, ticket ID
Call legs	Granular routing segments within a call, useful for tracing call paths
Agents activities	Per-agent metrics: calls handled, talk time, hold time, availability
Agents overviews	Aggregated view across all agents: status, queue position, availability
Account overviews	Account-wide totals: total calls, missed calls, average wait time
Current queue activities	Live snapshot of your call queues: calls waiting, agents available
Phone numbers	Numbers provisioned in Zendesk Talk with line settings
Addresses	SIP or phone address configs linked to your account
IVRs	IVR system records with enabled/disabled status
IVR menus	Menu items, digit mappings, and prompt settings
IVR routes	Routing logic: what happens after a menu selection
Greetings	Audio greeting records used in IVR or hold flows
Greeting categories	Labels that group greetings for easier management

Calls

Call fields

Field	Description
id	Unique call identifier
created_at	Timestamp when the call started
duration	Total call duration in seconds
direction	Inbound or outbound
status	Call outcome (completed, missed, voicemail, etc.)
agent_id	ID of the assigned agent
ticket_id	Linked Zendesk Support ticket
line_id	Phone number the call came in on
recording_url	Link to call recording if enabled
wait_time	Seconds the caller waited before being answered
hold_time	Total hold time during the call
talk_time	Active talk time in seconds

Call legs

Call leg fields

Field	Description
id	Unique leg identifier
call_id	Parent call this leg belongs to
agent_id	Agent who handled this leg
type	Leg type (agent, external transfer, etc.)
duration	Duration of this segment
started_at	Timestamp when this leg began

Agent activity and performance

Agents activities fields

Field	Description
agent_id	Agent identifier
agent_name	Agent display name
calls_count	Number of calls handled
talk_time	Total talk time
hold_time	Total hold time
avg_talk_time	Average talk time per call
missed_calls	Number of missed calls
availability	Current availability status

Agents overviews fields

Field	Description
online_agents	Count of agents currently online
calls_active	Calls currently in progress
agents_on_call	Agents currently on a call
agents_offline	Agents currently offline

Queue and account metrics

Account overviews fields

Field	Description
total_calls	All calls in the period
missed_calls	Calls that went unanswered
avg_wait_time	Average caller wait time
voicemails	Voicemails received

Current queue activities fields

Field	Description
calls_waiting	Callers currently on hold in queue
agents_online	Online agents available for calls
longest_wait	Longest current wait time in seconds

Common metric combinations

• Calls + Agents activities — Join on agent_id to see how each agent's call volume breaks down by outcome

• Calls + Call legs — Join on call_id to trace routing paths for escalated or transferred calls

• Account overviews + Agents overviews — Combine for a full snapshot of team capacity vs. demand

• Agents activities across multiple time periods — Use Append to stack weekly exports for trend analysis

Use cases by role

Support managers

• Track missed call rates by agent and by time period to identify staffing gaps

• Compare talk_time vs. hold_time ratios to spot agents who put customers on hold excessively

• Export Calls with ticket IDs and join to Zendesk Support ticket data to measure call-to-resolution rates

Operations

• Monitor Current queue activities in a live dashboard (Google Sheets or Looker Studio) to flag when queues back up

• Analyze IVR routes and menus to identify dead ends or underused routing paths

• Use Account overviews to report on overall phone channel volume for capacity planning

Analysts

• Aggregate call data by week or month using the Aggregate transformation to surface volume trends

• Join Call legs to Calls to calculate how often calls are transferred and to whom

• Feed call summaries into ChatGPT or Claude to auto-generate performance narratives

Platform-specific notes

• The start_date parameter only applies to Calls and Call legs — all other entities return their full current dataset

• Zendesk Talk does not expose voicemail transcripts or recording audio through the API — only the recording_url is available

• Current queue activities and Agents overviews reflect real-time state at the moment of the data flow run, not historical snapshots

• agent_id in Talk data maps to the same agent IDs used in Zendesk Support, making cross-source joins straightforward

Zendesk Talk common issues

Connection issues

Authentication fails when I enter my API token

Zendesk Talk uses a combined credential format. Make sure you're entering your email address (not just your username) and the API token (not your account password). In Zendesk, API tokens are found under Admin Center → Apps and integrations → Zendesk API → API tokens. Also confirm that API access is enabled on that same page — it can be toggled off.

My subdomain isn't being accepted

Enter only the subdomain portion — for example, if your Zendesk URL is acme.zendesk.com, enter acme. Do not include https://, .zendesk.com, or any trailing slashes.

Missing data

Calls or Call legs return no data

Both entities require a start date. If no start date is set, the export may return empty results. Use the date picker to set a start date that covers the period you need. Also confirm that calls were actually made in that period — if the account was newly set up, there may be no records yet.

Current queue activities or Agents overviews show unexpected zeros

These entities reflect the real-time state at the moment the data flow runs. If you run the data flow outside business hours or when no agents are online, values like calls_waiting or agents_on_call will legitimately be zero. Schedule runs during active hours if you need meaningful snapshots.

IVR menus or IVR routes return no rows

These entities only return data if IVRs are configured in your Zendesk Talk account. If your account uses simple line routing without IVRs, these entities will be empty.

Permission errors

I get a 403 Forbidden error

The agent account whose credentials you're using may not have sufficient permissions. Zendesk Talk API access typically requires an Administrator role. Ask your Zendesk admin to either grant admin rights to your account or generate a dedicated API token using an admin account.

Call recordings are missing from the Calls entity

The recording_url field only appears if call recording is enabled for your Zendesk Talk plan and the specific line. Additionally, access to recordings may be restricted by role — agents may see their own recordings, but not others'. Confirm recording settings under Admin Center → Channels → Talk.

Data discrepancies

Call counts in Coupler.io don't match the Zendesk Talk dashboard

Zendesk Talk dashboards often apply their own date/time filters and may use the account's local timezone. Coupler.io exports timestamps in UTC. Check that you're comparing the same time window accounting for timezone differences. Also note that Zendesk Talk may count abandoned calls differently depending on the dashboard view.

Rate limits

The data flow fails with a rate limit error

Zendesk's API enforces rate limits that vary by plan (typically 700 requests per minute for most plans). Exporting very large date ranges for Calls or Call legs in a single run can trigger these limits. Narrow your start date to a shorter window and run multiple data flows for different periods if needed.

Zendesk Talk FAQ

Which Zendesk Talk entities support date filtering?

Only Calls and Call legs support a start date parameter. All other entities (Agents activities, Agents overviews, Account overviews, Current queue activities, IVRs, Phone numbers, etc.) return their full current dataset regardless of any date setting.

Can I connect multiple Zendesk Talk accounts to the same data flow?

Yes. You can add multiple sources within a single data flow — one per Zendesk account. Use the Append transformation to combine call data from different accounts into a single output, which is useful if your organization runs separate Zendesk instances for different regions or brands.

How do I link Zendesk Talk calls to Zendesk Support tickets?

The Calls entity includes a ticket_id field that maps directly to ticket IDs in Zendesk Support. If you also have Zendesk Support connected to Coupler.io, use the Join transformation on ticket_id to combine call data with ticket details like resolution time, priority, and agent notes.

Why do Agents overviews and Current queue activities change every time I run the data flow?

Both of these entities reflect the live state of your Zendesk Talk account at the moment the data flow runs. They are not historical — each run overwrites the previous output. If you need to track changes over time, consider appending each run's output to a separate log sheet rather than replacing it.

Can I export call recordings through Coupler.io?

No. The Zendesk Talk API only provides a recording_url link in the Calls entity — it does not stream or export audio files. You'd need to access the recording URLs directly in Zendesk or download them via a separate tool.

What's the difference between Calls and Call legs?

A Call is the full interaction from start to finish. A Call leg is a segment within that call — for example, the initial inbound ring, a transfer to a different agent, or an external forwarding leg. If a call is transferred twice, it will have one Call record and three Call leg records. Use Call legs when you need to trace exactly how calls were routed.

Can I use Zendesk Talk data with AI tools?

Yes. Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Perplexity, Cursor, and OpenClaw. You could, for example, send a weekly export of agent activity metrics to ChatGPT to generate a plain-language performance summary, or feed missed call trends to Claude for root-cause analysis.

Why are my IVR menus and IVR routes empty?

These entities only contain data if Interactive Voice Response is configured in your Zendesk Talk account. If your setup uses direct-to-agent routing without IVR menus, these entities will return no rows. Check under Admin Center → Channels → Talk → IVR to confirm whether IVR is enabled.

For a full breakdown of available fields per entity, see the Data Overview article. For help with authentication errors or missing data, check Common Issues.