Sigma Computing connector
Set up the Sigma Computing connector in Kaivo: authentication, configuration, the 8 BigQuery tables it syncs, and answers to common questions.
Sigma Computing connector pricing, tier and credits on kaivo.ioKaivo is a fully managed data platform that syncs your Sigma Computing 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 data from Sigma Computing instead of moving it.
What is the Sigma Computing connector
Section titled “What is the Sigma Computing connector”Sync your Sigma Computing metadata into BigQuery with Kaivo to audit workbooks, datasets, and usage across your workspace.
| Category | Tech |
|---|---|
| Authentication | API key |
| Setup | Self-service |
Getting started with the Sigma Computing connector
Section titled “Getting started with the Sigma Computing connector”- Sign up for Kaivo and create a workspace.
- Connect your Sigma Computing 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 Sigma Computing
Section titled “Authenticating Sigma Computing”Authenticate with your Client secret.
| Field | Description |
|---|---|
| Client secret |
Prerequisites
Sigma Computing authenticates with your own API credentials:
- In your Sigma account, go to Account > General Settings and check the Site section to find the Base URL for your cloud provider. See Sigma API reference for the correct URL per cloud provider.
- Go to Developer Access and click Create to generate a Client ID and Client Secret.
Then enter those values below.
Need help, or want an easier way to connect? Reach our team via the chat in the bottom-right corner.
Configuring the Sigma Computing connector
Section titled “Configuring the Sigma Computing connector”When you set up the connector, you provide:
| Field | Description |
|---|---|
| Client ID | |
| Base URL | |
| The base url of your sigma organization |
|
Tables and columns synced from Sigma Computing
Section titled “Tables and columns synced from Sigma Computing”Kaivo syncs 8 tables from Sigma Computing into a dedicated dataset in your BigQuery warehouse. Click any table to see its columns and types.
connections (28 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
type |
STRING |
|
account |
STRING |
|
connection_id |
STRING |
|
created_at |
STRING |
|
created_by |
STRING |
|
friendly_name |
BOOL |
|
host |
STRING |
|
is_archived |
BOOL |
|
is_audit_log |
BOOL |
|
is_sample |
BOOL |
|
last_active_at |
STRING |
|
name |
STRING |
|
organization_id |
STRING |
|
pool_sizes__adhoc_pool_size |
FLOAT64 |
|
pool_sizes__catalog_pool_size |
FLOAT64 |
|
pool_sizes__is_pool_configured |
BOOL |
|
pool_sizes__result_pool_size |
FLOAT64 |
|
pool_sizes__schedule_pool_size |
FLOAT64 |
|
role |
STRING |
|
timeout__default |
FLOAT64 |
|
updated_at |
STRING |
|
updated_by |
STRING |
|
use_oauth |
BOOL |
|
user |
STRING |
|
warehouse |
STRING |
|
write_access |
BOOL |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: connections__writebacks
Section titled “Subtable: connections__writebacks”| 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. |
database |
STRING |
|
schema |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
datasets (10 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
description |
STRING |
|
created_at |
STRING |
|
created_by |
STRING |
|
dataset_id |
STRING |
|
name |
STRING |
|
updated_at |
STRING |
|
updated_by |
STRING |
|
url |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
files (16 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
type |
STRING |
|
created_at |
STRING |
|
created_by |
STRING |
|
id |
STRING |
|
is_archived |
BOOL |
|
name |
STRING |
|
owner_id |
STRING |
|
parent_id |
STRING |
|
parent_url_id |
STRING |
|
path |
STRING |
|
permission |
STRING |
|
updated_at |
STRING |
|
updated_by |
STRING |
|
url_id |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
members (14 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
created_at |
STRING |
|
created_by |
STRING |
|
email |
STRING |
|
first_name |
STRING |
|
home_folder_id |
STRING |
|
last_name |
STRING |
|
member_id |
STRING |
|
member_type |
STRING |
|
organization_id |
STRING |
|
updated_at |
STRING |
|
updated_by |
STRING |
|
user_kind |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
teams (10 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
description |
STRING |
|
created_at |
STRING |
|
created_by |
STRING |
|
name |
STRING |
|
team_id |
STRING |
|
updated_at |
STRING |
|
updated_by |
STRING |
|
visibility |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
templates (12 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
created_at |
STRING |
|
created_by |
STRING |
|
latest_version |
FLOAT64 |
|
name |
STRING |
|
path |
STRING |
|
template_id |
STRING |
|
template_url_id |
STRING |
|
updated_at |
STRING |
|
updated_by |
STRING |
|
url |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
workbooks (13 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
created_at |
STRING |
|
created_by |
STRING |
|
latest_version |
FLOAT64 |
|
name |
STRING |
|
owner_id |
STRING |
|
path |
STRING |
|
updated_at |
STRING |
|
updated_by |
STRING |
|
url |
STRING |
|
workbook_id |
STRING |
|
workbook_url_id |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
workspaces (8 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
created_at |
STRING |
|
created_by |
STRING |
|
name |
STRING |
|
updated_at |
STRING |
|
updated_by |
STRING |
|
workspace_id |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
How the Sigma Computing sync works
Section titled “How the Sigma Computing sync works”After the first load, Kaivo keeps your BigQuery warehouse up to date for you. Where Sigma Computing 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 Sigma Computing?
Section titled “How long does the initial sync take for Sigma Computing?”It depends on how much history is in your Sigma Computing 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 Sigma Computing’s schema changes?
Section titled “What happens when Sigma Computing’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 Sigma Computing, 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 Sigma Computing 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 Sigma Computing connector in Kaivo and all of its synced data is deleted with it.
Common use cases for Sigma Computing data
Section titled “Common use cases for Sigma Computing data”Content inventory
Section titled “Content inventory”Use workbooks and datasets to document what exists and how it is organised.
Source mapping
Section titled “Source mapping”Use connections to track which sources your workbooks rely on.
Access review
Section titled “Access review”Join members with teams to review who can access your analytics.
Use Sigma Computing data in your AI and BI tools
Section titled “Use Sigma Computing data in your AI and BI tools”Once Sigma Computing 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 Sigma Computing 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 Sigma Computing connector pricing and plan details.