Skip to main content
Connectors

Dixa connector

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

Written By Lauri Raivio

Last updated 16 days ago

Kaivo is a fully managed data platform that syncs your Dixa 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.

What is the Dixa connector

Sync your Dixa conversations and messages into BigQuery with Kaivo to analyse support volume and response times alongside the rest of your data.

CategoryCustomer Service
AuthenticationAPI key
SetupSelf-service

Getting started with the Dixa connector

  1. Sign up for Kaivo and create a workspace.
  2. Connect your Dixa 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.

Authenticating Dixa

Authenticate with your API Token.

FieldDescription
API Token

You can create the API token by following Dixa's instructions. The name of the token can be for example "kaivo".

Configuring the Dixa connector

When you set up the connector, you provide:

FieldDescription
Start date

Any data before this date will not be fetched.

Tables and columns synced from Dixa

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

ColumnTypeDescription
_kaivo_idSTRINGPrimary key that uniquely identifies the row. Auto-generated by Kaivo.
anonymized_atINT64
assigned_atINT64
assignee_emailSTRING
assignee_idSTRING
assignee_nameSTRING
assignee_phone_numberSTRING
closed_atINT64
created_atINT64
directionSTRING
dixa_email_integration_idSTRING
dixa_email_integration_sender_nameSTRING
facebook_page_idSTRING
facebook_page_nameSTRING
forwarding_emailSTRING
from_provisioned_phone_number_idSTRING
from_provisioned_phone_number_nameSTRING
handling_durationINT64
idINT64
initial_channelSTRING
last_message_created_atINT64
originating_countrySTRING
queue_idSTRING
queue_nameSTRING
queued_atINT64
rating_messageSTRING
rating_scoreINT64
requester_emailSTRING
requester_idSTRING
requester_nameSTRING
requester_phone_numberSTRING
statusSTRING
subjectSTRING
to_provisioned_phone_number_idSTRING
to_provisioned_phone_number_nameSTRING
total_durationINT64
transfer_timeINT64
transferee_nameSTRING
transferee_numberSTRING
updated_atINT64
widget_idSTRING
widget_nameSTRING
_kaivo_extracted_atTIMESTAMPTimestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: conversation_export__conversation_wrapup_notes

ColumnTypeDescription
_kaivo_parent_idSTRINGForeign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
_kaivo_idSTRINGPrimary key that uniquely identifies the row. Auto-generated by Kaivo.
valueSTRING
_kaivo_extracted_atTIMESTAMPTimestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: conversation_export__custom_fields

ColumnTypeDescription
_kaivo_parent_idSTRINGForeign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
_kaivo_idSTRINGPrimary key that uniquely identifies the row. Auto-generated by Kaivo.
archivedBOOL
attribute_idSTRING
data_typeSTRING
identifierSTRING
_kaivo_extracted_atTIMESTAMPTimestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: conversation_export__custom_fields__value

ColumnTypeDescription
_kaivo_parent_idSTRINGForeign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
_kaivo_idSTRINGPrimary key that uniquely identifies the row. Auto-generated by Kaivo.
valueJSON
_kaivo_extracted_atTIMESTAMPTimestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: conversation_export__ratings

ColumnTypeDescription
_kaivo_parent_idSTRINGForeign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
_kaivo_idSTRINGPrimary key that uniquely identifies the row. Auto-generated by Kaivo.
rating_cancelled_timestampINT64
rating_created_timestampINT64
rating_languageSTRING
rating_messageSTRING
rating_modified_timestampINT64
rating_offered_timestampINT64
rating_rated_timestampINT64
rating_scheduled_for_timestampINT64
rating_scheduled_timestampINT64
rating_scoreINT64
rating_statusSTRING
rating_typeSTRING
rating_unscheduled_timestampINT64
_kaivo_extracted_atTIMESTAMPTimestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: conversation_export__requester_additional_emails

ColumnTypeDescription
_kaivo_parent_idSTRINGForeign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
_kaivo_idSTRINGPrimary key that uniquely identifies the row. Auto-generated by Kaivo.
valueSTRING
_kaivo_extracted_atTIMESTAMPTimestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: conversation_export__requester_additional_phone_numbers

ColumnTypeDescription
_kaivo_parent_idSTRINGForeign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
_kaivo_idSTRINGPrimary key that uniquely identifies the row. Auto-generated by Kaivo.
valueSTRING
_kaivo_extracted_atTIMESTAMPTimestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: conversation_export__tags

ColumnTypeDescription
_kaivo_parent_idSTRINGForeign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
_kaivo_idSTRINGPrimary key that uniquely identifies the row. Auto-generated by Kaivo.
valueSTRING
_kaivo_extracted_atTIMESTAMPTimestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: conversation_export__tags_info

ColumnTypeDescription
_kaivo_parent_idSTRINGForeign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
_kaivo_idSTRINGPrimary key that uniquely identifies the row. Auto-generated by Kaivo.
_kaivo_extracted_atTIMESTAMPTimestamp that shows when the row was extracted. Auto-generated by Kaivo.
ColumnTypeDescription
_kaivo_idSTRINGPrimary key that uniquely identifies the row. Auto-generated by Kaivo.
author_emailSTRING
author_nameSTRING
chat_input_answerSTRING
chat_input_questionSTRING
chat_menu_textSTRING
created_atINT64
csidINT64
directionSTRING
durationINT64
fromSTRING
from_phone_numberSTRING
idSTRING
initial_channelSTRING
is_automated_messageBOOL
recording_urlSTRING
textSTRING
to_phone_numberSTRING
voicemail_urlSTRING
_kaivo_extracted_atTIMESTAMPTimestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: message_export__attached_files

ColumnTypeDescription
_kaivo_parent_idSTRINGForeign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
_kaivo_idSTRINGPrimary key that uniquely identifies the row. Auto-generated by Kaivo.
valueSTRING
_kaivo_extracted_atTIMESTAMPTimestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: message_export__bcc

ColumnTypeDescription
_kaivo_parent_idSTRINGForeign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
_kaivo_idSTRINGPrimary key that uniquely identifies the row. Auto-generated by Kaivo.
valueSTRING
_kaivo_extracted_atTIMESTAMPTimestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: message_export__cc

ColumnTypeDescription
_kaivo_parent_idSTRINGForeign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
_kaivo_idSTRINGPrimary key that uniquely identifies the row. Auto-generated by Kaivo.
valueSTRING
_kaivo_extracted_atTIMESTAMPTimestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: message_export__to

ColumnTypeDescription
_kaivo_parent_idSTRINGForeign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
_kaivo_idSTRINGPrimary key that uniquely identifies the row. Auto-generated by Kaivo.
valueSTRING
_kaivo_extracted_atTIMESTAMPTimestamp that shows when the row was extracted. Auto-generated by Kaivo.

How the Dixa sync works

After the first load, Kaivo keeps your BigQuery warehouse up to date for you. Where Dixa 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.

Frequently asked questions

How long does the initial sync take for Dixa?

It depends on how much history is in your Dixa 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.

Can I sync only some tables or columns?

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 Dixa'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 Dixa, 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?

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 Dixa 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 Dixa connector in Kaivo and all of its synced data is deleted with it.

Common use cases for Dixa data

Support volume

Use conversation_export to track ticket volume by channel and over time.

Response times

Analyse message_export timestamps to measure first response and resolution times.

Agent workload

Break conversations down by agent and queue to balance workload.

Support and product together

Join Dixa conversations with product or order data in BigQuery to connect support to the customer journey.

Use Dixa data in your AI and BI tools

Once Dixa 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 Dixa data.

Claude

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

Power BI

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

Data Studio

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

Tableau

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

Google Sheets

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

Excel

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

Metabase

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

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

Was this helpful?

Still need help? Share an idea