Perk connector

Set up the Perk connector in Kaivo: authentication, configuration, the 7 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 Perk 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 Perk connector

Sync your Perk travel and expense data into BigQuery with Kaivo to analyse trips, bookings, spend, and cost centres in one place.

Category	Finance & Payments
Authentication	API key
Setup	Self-service

Getting started with the Perk connector

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

Authenticate with your API Key.

Field	Description
API Key

Configuring the Perk connector

When you set up the connector, you provide:

Field	Description
Start Date	Any data before this date will not be fetched.

Tables and columns synced from Perk

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

bookings (13 columns)

Column	Type	Description
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`type`	`STRING`
`id`	`STRING`
`end`	`STRING`
`start`	`STRING`
`status`	`STRING`
`trip_id`	`STRING`
`location__name`	`STRING`
`location__address`	`STRING`
`location__latitude`	`STRING`
`location__longitude`	`STRING`
`modified`	`STRING`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: bookings__legs

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

Subtable: bookingslegssegments

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.
`origin__time`	`STRING`
`origin__location__name`	`STRING`
`origin__location__address`	`STRING`
`origin__location__latitude`	`STRING`
`origin__location__iata_code`	`STRING`
`origin__location__longitude`	`STRING`
`destination__time`	`STRING`
`destination__location__name`	`STRING`
`destination__location__address`	`STRING`
`destination__location__latitude`	`STRING`
`destination__location__iata_code`	`STRING`
`destination__location__longitude`	`STRING`
`external_id`	`STRING`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: bookings__references

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.

cost_centers (5 columns)

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

invoices (28 columns)

Column	Type	Description
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`pdf`	`STRING`
`mode`	`STRING`
`total`	`STRING`
`status`	`STRING`
`to_date`	`STRING`
`currency`	`STRING`
`due_date`	`STRING`
`from_date`	`STRING`
`reference`	`STRING`
`profile_id`	`STRING`
`issuing_date`	`STRING`
`profile_name`	`STRING`
`serial_number`	`STRING`
`billing_period`	`STRING`
`billing_information__city`	`STRING`
`billing_information__legal_name`	`STRING`
`billing_information__vat_number`	`STRING`
`billing_information__postal_code`	`STRING`
`billing_information__country_name`	`STRING`
`billing_information__address_line_1`	`STRING`
`billing_information__address_line_2`	`STRING`
`travelperk_bank_account__bic`	`STRING`
`travelperk_bank_account__bank_name`	`STRING`
`travelperk_bank_account__reference`	`STRING`
`travelperk_bank_account__account_number`	`STRING`
`credit_used_for_customer_payment`	`STRING`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: invoices__taxes_summary

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

invoices_lines (52 columns)

Column	Type	Description
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`description`	`STRING`
`metadata__booker__name`	`STRING`
`metadata__booker__email`	`STRING`
`metadata__booker__external_id`	`STRING`
`metadata__vendor__code`	`STRING`
`metadata__vendor__name`	`STRING`
`metadata__service`	`STRING`
`metadata__trip_id`	`FLOAT64`
`metadata__end_date`	`STRING`
`metadata__trip_name`	`STRING`
`metadata__start_date`	`STRING`
`metadata__cost_center`	`STRING`
`metadata__out_of_policy`	`BOOL`
`metadata__related_vertical`	`STRING`
`metadata__service_location__origin__city`	`STRING`
`metadata__service_location__origin__code`	`STRING`
`metadata__service_location__origin__name`	`STRING`
`metadata__service_location__origin__country`	`STRING`
`metadata__service_location__origin__latitude`	`STRING`
`metadata__service_location__origin__longitude`	`STRING`
`metadata__service_location__origin__country_code`	`STRING`
`metadata__service_location__destination__city`	`STRING`
`metadata__service_location__destination__code`	`STRING`
`metadata__service_location__destination__name`	`STRING`
`metadata__service_location__destination__country`	`STRING`
`metadata__service_location__destination__latitude`	`STRING`
`metadata__service_location__destination__longitude`	`STRING`
`metadata__service_location__destination__country_code`	`STRING`
`metadata__service_location__hotel_location__city`	`STRING`
`metadata__service_location__hotel_location__country`	`STRING`
`metadata__service_location__hotel_location__latitude`	`STRING`
`metadata__service_location__hotel_location__longitude`	`STRING`
`metadata__service_location__hotel_location__country_code`	`STRING`
`id`	`STRING`
`currency`	`STRING`
`due_date`	`STRING`
`quantity`	`FLOAT64`
`profile_id`	`STRING`
`tax_amount`	`STRING`
`tax_regime`	`STRING`
`unit_price`	`STRING`
`expense_date`	`STRING`
`invoice_mode`	`STRING`
`issuing_date`	`STRING`
`profile_name`	`STRING`
`total_amount`	`STRING`
`invoice_status`	`STRING`
`tax_percentage`	`STRING`
`invoice_serial_number`	`STRING`
`non_taxable_unit_price`	`STRING`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: invoices_linesmetadatalabels

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: invoices_linesmetadataapprovers

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: invoices_linesmetadatatravelers

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

profiles (13 columns)

Column	Type	Description
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`id`	`STRING`
`name`	`STRING`
`currency`	`STRING`
`billing_period`	`STRING`
`billing_information__city`	`STRING`
`billing_information__legal_name`	`STRING`
`billing_information__vat_number`	`STRING`
`billing_information__postal_code`	`STRING`
`billing_information__address_line_1`	`STRING`
`billing_information__address_line_2`	`STRING`
`payment_method_type`	`STRING`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

trips (23 columns)

Column	Type	Description
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`id`	`STRING`
`end`	`STRING`
`start`	`STRING`
`status`	`STRING`
`modified`	`STRING`
`booker_id`	`STRING`
`trip_name`	`STRING`
`end_location__name`	`STRING`
`end_location__address`	`STRING`
`end_location__latitude`	`STRING`
`end_location__iata_code`	`STRING`
`end_location__longitude`	`STRING`
`start_location__name`	`STRING`
`start_location__address`	`STRING`
`start_location__latitude`	`STRING`
`start_location__iata_code`	`STRING`
`start_location__longitude`	`STRING`
`end_datetime_utc`	`STRING`
`end_datetime_local`	`STRING`
`start_datetime_utc`	`STRING`
`start_datetime_local`	`STRING`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

users (14 columns)

Column	Type	Description
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`id`	`STRING`
`name__title`	`STRING`
`name__last_name`	`STRING`
`name__first_name`	`STRING`
`name__middle_name`	`STRING`
`email`	`STRING`
`active`	`BOOL`
`locale`	`STRING`
`user_name`	`STRING`
`emergency_contact__name`	`STRING`
`emergency_contact__phone`	`STRING`
`preferred_language`	`STRING`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: users__phone_numbers

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.

How the Perk sync works

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

It depends on how much history is in your Perk 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 Perk'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 Perk, 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 Perk 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 Perk connector in Kaivo and all of its synced data is deleted with it.

Common use cases for Perk data

Travel spend

Use trips and bookings to track travel volume and cost over time.

Cost centre view

Join invoices_lines with cost_centers to break down spend.

Finance context

Use invoices to report travel spend alongside your finance data.

Use Perk data in your AI and BI tools

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

Chargebee: Sync Chargebee to BigQuery.
ChartMogul: Sync ChartMogul to BigQuery.
Fennoa: Sync Fennoa to BigQuery.
Fortnox: Sync Fortnox to BigQuery.
FreshBooks: Sync FreshBooks to BigQuery.
PayPal Enterprise Payments: Sync PayPal Enterprise Payments to BigQuery.

Was this helpful?

Still need help? Share an idea