Chift connector

Set up the Chift connector in Kaivo: authentication, configuration, the 3 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 Chift 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 payment and finance data instead of moving it.

What is the Chift connector

Sync your Chift integration data into BigQuery with Kaivo to monitor connections, sync reliability, and consumer activity across integrations.

Category	Finance & Payments, Tech
Authentication	API key
Setup	Self-service

Getting started with the Chift connector

Sign up for Kaivo and create a workspace.
Connect your Chift account.
Choose which tables to sync.
Wait for the initial sync to finish.
Query your data in BigQuery or your favourite AI or BI tool.

Authenticating Chift

Authenticate with your Client Secret.

Field	Description
Client Secret	Client Secret from your Chift API key. Copy it when the key is created, as it is shown only once.

Configuring the Chift connector

When you set up the connector, you provide:

Field	Description
Client ID	Client ID from your Chift API key. Create an API key in your Chift dashboard to get the Account ID, Client ID, and Client Secret together. See Chift's docs.
Account ID	Account ID from your Chift API key.

Tables and columns synced from Chift

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

connections (10 columns)

Column	Type	Description
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`api`	`STRING`
`data__folder_id`	`STRING`
`name`	`STRING`
`status`	`STRING`
`consumerid`	`STRING`
`integration`	`STRING`
`connectionid`	`STRING`
`integrationid`	`FLOAT64`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

consumers (7 columns)

Column	Type	Description
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`name`	`STRING`
`email`	`STRING`
`consumerid`	`STRING`
`redirect_url`	`STRING`
`internal_reference`	`STRING`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

syncs (4 columns)

Column	Type	Description
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`name`	`STRING`
`syncid`	`STRING`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: syncs__flows

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.
`description`	`STRING`
`id`	`STRING`
`name`	`STRING`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: syncsflowsconfig__datastores

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.
`id`	`STRING`
`name`	`STRING`
`status`	`STRING`
`definition__search_column`	`STRING`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: syncsflowsconfigdatastoresdefinition__columns

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.
`type`	`STRING`
`name`	`STRING`
`title`	`STRING`
`optional`	`BOOL`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: syncsflowsconfig__custom_fields

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.
`type`	`STRING`
`value`	`STRING`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: syncsflowsconfig__definition_fields

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.
`type`	`STRING`
`name`	`STRING`
`title`	`STRING`
`default`	`STRING`
`optional`	`BOOL`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: syncsflowsconfig__definition_fields__data

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.
`title`	`STRING`
`value`	`STRING`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: syncsflowstriggers

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.
`type`	`STRING`
`id`	`STRING`
`visible`	`BOOL`
`priority`	`STRING`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: syncsflowstriggers__cronschedules

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.
`value`	`STRING`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: syncs__mappings

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.
`description`	`STRING`
`name`	`STRING`
`display_order`	`FLOAT64`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: syncsmappingssub_mappings

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`
`source_field__type`	`STRING`
`source_field__name`	`STRING`
`target_field__type`	`STRING`
`target_field__name`	`STRING`
`target_field__api_route`	`STRING`
`display_order`	`FLOAT64`
`display_delete`	`BOOL`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: syncsmappingssub_mappings__source_field__values

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.
`id`	`STRING`
`label`	`STRING`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: syncsmappingssub_mappings__target_field__display_condition__in

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.
`value`	`JSON`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: syncs__consumers

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.
`value`	`STRING`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: syncs__connections

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.
`one_api`	`FLOAT64`
`display_order`	`FLOAT64`
`display_hidden`	`BOOL`
`connection_type`	`FLOAT64`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

How the Chift sync works

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

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

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

Common use cases for Chift data

Connection monitoring

Use connections and syncs to track which integrations run and their health.

Consumer view

Join consumers with connections to see integration coverage across your customers.

Sync reliability

Use syncs to find failing integrations and patterns over time.

Use Chift data in your AI and BI tools

Once Chift 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 Chift 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 Chift connector pricing and plan details.

Adform: Sync Adform to BigQuery.
Amplitude: Sync Amplitude to BigQuery.
Auth0: Sync Auth0 to BigQuery.
Chargebee: Sync Chargebee to BigQuery.
ChartMogul: Sync ChartMogul to BigQuery.
Convex: Sync Convex to BigQuery.

Was this helpful?

Still need help? Share an idea