ZeroWaste connector
Set up the ZeroWaste connector in Kaivo: authentication, configuration, the 4 BigQuery tables it syncs, and answers to common questions.
ZeroWaste connector pricing, tier and credits on kaivo.ioKaivo 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
Section titled “What is the ZeroWaste connector”Sync your ZeroWaste data into BigQuery with Kaivo to report on waste operations alongside the rest of your business.
| Category | ERP |
|---|---|
| Authentication | API key |
| Setup | Self-service |
Getting started with the ZeroWaste connector
Section titled “Getting started with the ZeroWaste connector”- Sign up for Kaivo and create a workspace.
- Connect your ZeroWaste 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 ZeroWaste
Section titled “Authenticating ZeroWaste”Authenticate with your API Key.
| Field | Description |
|---|---|
| API Key |
Configuring the ZeroWaste connector
Section titled “Configuring the ZeroWaste connector”When you set up the connector, you provide:
| Field | Description |
|---|---|
| App ID | |
| Start Date | |
| Any data before this date will not be fetched. |
|
Tables and columns synced from ZeroWaste
Section titled “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.
customer (15 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
id |
INT64 |
|
name |
STRING |
|
customernumber |
STRING |
|
companycode |
STRING |
|
email |
STRING |
|
phone |
STRING |
|
address__streetaddress |
STRING |
|
address__postalcode |
STRING |
|
address__city |
STRING |
|
address__country |
STRING |
|
description |
STRING |
|
archived |
INT64 |
|
active |
INT64 |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: customer__units
Section titled “Subtable: customer__units”| 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 |
INT64 |
|
customer_id |
INT64 |
|
name |
STRING |
|
customernumber |
STRING |
|
companycode |
STRING |
|
juridical_type |
INT64 |
|
origin_code |
INT64 |
|
property_identifier |
STRING |
|
email |
STRING |
|
phone |
STRING |
|
address__streetaddress |
STRING |
|
address__postalcode |
STRING |
|
address__city |
STRING |
|
address__country |
STRING |
|
contact |
STRING |
|
description |
STRING |
|
description2 |
STRING |
|
archived |
INT64 |
|
active |
INT64 |
|
coordinates__lat |
FLOAT64 |
|
coordinates__lng |
FLOAT64 |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
document (26 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
id |
INT64 |
|
root_id |
INT64 |
|
actualdate |
STRING |
|
customer_id |
INT64 |
|
customer_name |
STRING |
|
unit_id |
INT64 |
|
unit_name |
STRING |
|
transporter_id |
INT64 |
|
transporter_name |
STRING |
|
master_transporter_id |
INT64 |
|
master_transporter_name |
STRING |
|
plant_id |
INT64 |
|
plant_name |
STRING |
|
material_id |
INT64 |
|
material_name_fi |
STRING |
|
material_name_sv |
STRING |
|
material_name_en |
STRING |
|
ewc |
STRING |
|
unittype |
STRING |
|
weight |
FLOAT64 |
|
volume |
FLOAT64 |
|
amount |
FLOAT64 |
|
vehicle_licenceplate |
STRING |
|
username |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
material (35 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
id |
INT64 |
|
names__fi |
STRING |
|
names__sv |
STRING |
|
names__en |
STRING |
|
unit |
STRING |
|
ewc |
STRING |
|
density__unit |
STRING |
|
density__density |
FLOAT64 |
|
transportcode |
STRING |
|
code_un__code |
STRING |
|
code_un__names__fi |
STRING |
|
code_un__names__sv |
STRING |
|
code_un__names__en |
STRING |
|
code_rd__code |
STRING |
|
code_rd__names__fi |
STRING |
|
code_rd__names__sv |
STRING |
|
code_rd__names__en |
STRING |
|
code_h__code |
STRING |
|
code_h__names__fi |
STRING |
|
code_h__names__sv |
STRING |
|
code_h__names__en |
STRING |
|
packaging_type__code |
STRING |
|
packaging_type__names__fi |
STRING |
|
packaging_type__names__sv |
STRING |
|
packaging_type__names__en |
STRING |
|
physical_state__code |
STRING |
|
physical_state__names__fi |
STRING |
|
physical_state__names__sv |
STRING |
|
physical_state__names__en |
STRING |
|
materialgroup__id |
STRING |
|
materialgroup__names__fi |
STRING |
|
materialgroup__names__sv |
STRING |
|
materialgroup__names__en |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
plant (15 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
id |
INT64 |
|
name |
STRING |
|
companycode |
STRING |
|
email |
STRING |
|
phone |
STRING |
|
common_plant |
INT64 |
|
active |
INT64 |
|
address__streetaddress |
STRING |
|
address__postalcode |
STRING |
|
address__city |
STRING |
|
address__country |
STRING |
|
coordinates__lat |
FLOAT64 |
|
coordinates__lng |
FLOAT64 |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
How the ZeroWaste sync works
Section titled “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
Section titled “Frequently asked questions”How long does the initial sync take for ZeroWaste?
Section titled “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?
Section titled “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?
Section titled “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?
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 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
Section titled “Common use cases for ZeroWaste data”Operations reporting
Section titled “Operations reporting”Track collections and volumes to monitor waste operations over time.
Cost and billing
Section titled “Cost and billing”Analyse invoices and services to monitor costs and revenue.
Efficiency analysis
Section titled “Efficiency analysis”Report on routes or sites to find where to improve efficiency.
Combine with finance
Section titled “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
Section titled “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
Section titled “Claude”Use Kaivo’s MCP server to give Claude secure, workspace-scoped access to your data. Setup guide →
Power BI
Section titled “Power BI”Microsoft’s BI tool with a native BigQuery connector. Supports direct query and scheduled refresh. Setup guide →
Data Studio
Section titled “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
Section titled “Tableau”The premium analytics standard, with native BigQuery integration. Setup guide →
Google Sheets
Section titled “Google Sheets”Use Connected Sheets to query BigQuery directly from a spreadsheet, with no SQL. Setup guide →
Connect via Power Query’s BigQuery connector. Setup guide →
Metabase
Section titled “Metabase”Open-source BI tool with strong BigQuery support. Setup guide →
See our pricing page for ZeroWaste connector pricing and plan details.
Related connectors
Section titled “Related connectors”- NetSuite: Sync NetSuite to BigQuery.
- NetSuite Saved Searches: Sync NetSuite Saved Searches to BigQuery.
- Finago Procountor: Sync Finago Procountor to BigQuery.
- Cin7 Core: Sync Cin7 Core to BigQuery.
- Dolibarr: Sync Dolibarr to BigQuery.
- Katana MRP: Sync Katana MRP to BigQuery.