Skip to content
Book a demoStart free
Connectors

Genesys connector

Set up the Genesys connector in Kaivo: authentication, configuration, the 6 BigQuery tables it syncs, and answers to common questions.

Genesys connector pricing, tier and credits on kaivo.io

Kaivo is a fully managed data platform that syncs your Genesys data into a Google BigQuery warehouse and keeps it up to date automatically. There is no pipeline to build and no infrastructure to run, so you can spend your time analysing your customer support data instead of moving it.

Sync your Genesys contact centre data into BigQuery with Kaivo to analyse call and conversation performance alongside the rest of your data.

CategoryCustomer Service
AuthenticationAPI key
SetupSelf-service

Getting started with the Genesys connector

Section titled “Getting started with the Genesys connector”
  1. Sign up for Kaivo and create a workspace.
  2. Connect your Genesys account.
  3. Choose which tables to sync.
  4. Wait for the initial sync to finish.
  5. Query your data in BigQuery or your favourite AI or BI tool.

Authenticate with your Client Secret.

Field Description
Client Secret
The OAuth 2.0 Client Secret corresponding to the Client ID above.

|

When you set up the connector, you provide:

Field Description
Base URL
The base URL of your Genesys Cloud region, e.g. https://api.mypurecloud.com for US East or https://api.euw2.pure.cloud for EU West 2. See the Genesys documentation for a full list of regional URLs.

| | Client ID |

The OAuth 2.0 Client ID for your Genesys Cloud OAuth client. Create one under Admin > Integrations > OAuth in your Genesys Cloud organization.

|

Kaivo syncs 6 tables from Genesys into a dedicated dataset in your BigQuery warehouse. Click any table to see its columns and types.

conversation_aggregates (4 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
group__queue_id STRING
interval STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: conversation_aggregates__metrics

Section titled “Subtable: conversation_aggregates__metrics”
Column Type Description
_kaivo_parent_id STRING Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
metric STRING
stats__count FLOAT64
stats__max FLOAT64
stats__min FLOAT64
stats__sum FLOAT64
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
conversation_details (31 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
conversation_id STRING
conversation_start STRING
conversation_end STRING
originating_direction STRING
division_id STRING
participant_id STRING
participant_name STRING
purpose STRING
user_id STRING
team_id STRING
flagged_reason STRING
external_contact_id STRING
external_organization_id STRING
wrap_up_code STRING
session_id STRING
queue_id STRING
queue_name STRING
media_type STRING
direction STRING
disconnect_type STRING
provider STRING
remote STRING
recording BOOL
outbound_campaign_id STRING
flow_in_type STRING
flow_out_type STRING
address_self STRING
session_start STRING
session_end STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
Column Type Description
_kaivo_parent_id STRING Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
name STRING
value FLOAT64
emit_date STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
queues (11 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
id STRING
name STRING
description STRING
date_created STRING
date_modified STRING
member_count INT64
skill_evaluation_method STRING
calling_party_name STRING
calling_party_number STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
teams (7 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
id STRING
name STRING
description STRING
date_modified STRING
member_count INT64
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
users (10 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
id STRING
name STRING
username STRING
email STRING
department STRING
title STRING
date_modified STRING
state STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
wrap_up_codes (6 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
id STRING
name STRING
date_created STRING
date_modified STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

After the first load, Kaivo keeps your BigQuery warehouse up to date for you. Where Genesys supports it, each sync pulls only new and changed records so it stays fast; otherwise it refreshes the whole table. Every record keeps its original ID, so you won’t get duplicate rows.

How long does the initial sync take for Genesys?

Section titled “How long does the initial sync take for Genesys?”

It depends on how much history is in your Genesys account. Most initial syncs finish within minutes, while large accounts can take a few hours. After that, syncs only fetch new and changed records, so they’re much faster.

Yes. You pick which tables to sync when you set up the connection and can change the selection later. Tables you don’t select are never copied to your warehouse.

What happens when Genesys’s schema changes?

Section titled “What happens when Genesys’s schema changes?”

New fields are never added automatically. You choose which fields to sync, so data you haven’t selected (sensitive personal data, for example) never lands in your warehouse. When a new field appears, it becomes available for you to add. What happens to removed or renamed fields depends on a table’s sync mode: full-refresh tables always match what’s currently in Genesys, so dropped fields disappear, while incremental tables keep their existing columns and history, so an old field stays and newly added fields fill in over time.

How do I handle GDPR or data deletion requests?

Section titled “How do I handle GDPR or data deletion requests?”

Your data lives in your own Kaivo-managed BigQuery warehouse, so the most direct option is to delete or anonymise specific records right in BigQuery. If you delete data in Genesys instead, full-refresh tables drop it on the next sync, while incremental tables keep it, so you would remove the row in BigQuery or ask us to run a full refresh. To remove everything, delete the Genesys connector in Kaivo and all of its synced data is deleted with it.

Use conversation_aggregates to track call and conversation volume by queue and over time.

Measure wait times, handle times, and abandonment to monitor service levels.

Analyse volume by time of day to plan staffing and reduce wait times.

Join Genesys data with your CRM in BigQuery to connect contacts to customers and outcomes.

Once Genesys data lands in your Kaivo-managed BigQuery warehouse, you can explore it with AI tools or any BI tool that connects to BigQuery. Here’s how the most common destinations work with Genesys data.

Use Kaivo’s MCP server to give Claude secure, workspace-scoped access to your data. Setup guide →

Microsoft’s BI tool with a native BigQuery connector. Supports direct query and scheduled refresh. Setup guide →

Free Google BI tool with native BigQuery support. One-click connection to your Kaivo warehouse; great for SMB teams on Google Workspace. Setup guide →

The premium analytics standard, with native BigQuery integration. Setup guide →

Use Connected Sheets to query BigQuery directly from a spreadsheet, with no SQL. Setup guide →

Connect via Power Query’s BigQuery connector. Setup guide →

Open-source BI tool with strong BigQuery support. Setup guide →

See our pricing page for Genesys connector pricing and plan details.