Skip to main content
Connectors

ZeroWaste connector

Set up the ZeroWaste connector in Kaivo: authentication, configuration, the 4 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 ZeroWaste 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 ERP data instead of moving it.

What is the ZeroWaste connector

Sync your ZeroWaste data into BigQuery with Kaivo to report on waste operations alongside the rest of your business.

CategoryERP
AuthenticationAPI key
SetupSelf-service

Getting started with the ZeroWaste connector

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

Authenticate with your API Key.

FieldDescription
API Key

Configuring the ZeroWaste connector

When you set up the connector, you provide:

FieldDescription
App ID
Start Date

Any data before this date will not be fetched.

Tables and columns synced from ZeroWaste

Kaivo syncs 4 tables from ZeroWaste 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.
idINT64
nameSTRING
customernumberSTRING
companycodeSTRING
emailSTRING
phoneSTRING
address__streetaddressSTRING
address__postalcodeSTRING
address__citySTRING
address__countrySTRING
descriptionSTRING
archivedINT64
activeINT64
_kaivo_extracted_atTIMESTAMPTimestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: customer__units

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.
idINT64
customer_idINT64
nameSTRING
customernumberSTRING
companycodeSTRING
juridical_typeINT64
origin_codeINT64
property_identifierSTRING
emailSTRING
phoneSTRING
address__streetaddressSTRING
address__postalcodeSTRING
address__citySTRING
address__countrySTRING
contactSTRING
descriptionSTRING
description2STRING
archivedINT64
activeINT64
coordinates__latFLOAT64
coordinates__lngFLOAT64
_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.
idINT64
root_idINT64
actualdateSTRING
customer_idINT64
customer_nameSTRING
unit_idINT64
unit_nameSTRING
transporter_idINT64
transporter_nameSTRING
master_transporter_idINT64
master_transporter_nameSTRING
plant_idINT64
plant_nameSTRING
material_idINT64
material_name_fiSTRING
material_name_svSTRING
material_name_enSTRING
ewcSTRING
unittypeSTRING
weightFLOAT64
volumeFLOAT64
amountFLOAT64
vehicle_licenceplateSTRING
usernameSTRING
_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.
idINT64
names__fiSTRING
names__svSTRING
names__enSTRING
unitSTRING
ewcSTRING
density__unitSTRING
density__densityFLOAT64
transportcodeSTRING
code_un__codeSTRING
code_un__names__fiSTRING
code_un__names__svSTRING
code_un__names__enSTRING
code_rd__codeSTRING
code_rd__names__fiSTRING
code_rd__names__svSTRING
code_rd__names__enSTRING
code_h__codeSTRING
code_h__names__fiSTRING
code_h__names__svSTRING
code_h__names__enSTRING
packaging_type__codeSTRING
packaging_type__names__fiSTRING
packaging_type__names__svSTRING
packaging_type__names__enSTRING
physical_state__codeSTRING
physical_state__names__fiSTRING
physical_state__names__svSTRING
physical_state__names__enSTRING
materialgroup__idSTRING
materialgroup__names__fiSTRING
materialgroup__names__svSTRING
materialgroup__names__enSTRING
_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.
idINT64
nameSTRING
companycodeSTRING
emailSTRING
phoneSTRING
common_plantINT64
activeINT64
address__streetaddressSTRING
address__postalcodeSTRING
address__citySTRING
address__countrySTRING
coordinates__latFLOAT64
coordinates__lngFLOAT64
_kaivo_extracted_atTIMESTAMPTimestamp that shows when the row was extracted. Auto-generated by Kaivo.

How the ZeroWaste sync works

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

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

Common use cases for ZeroWaste data

Operations reporting

Track collections and volumes to monitor waste operations over time.

Cost and billing

Analyse invoices and services to monitor costs and revenue.

Efficiency analysis

Report on routes or sites to find where to improve efficiency.

Combine with finance

Join ZeroWaste data with your finance data in BigQuery for a full view.

Use ZeroWaste data in your AI and BI tools

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

Was this helpful?

Still need help? Share an idea