Skip to main content
Kadoa configures the integration for you through the Support Center.

Before you begin

  • A Snowflake role with IMPORT SHARE and CREATE DATABASE privileges. ACCOUNTADMIN has both.
  • Access to a Snowflake warehouse for queries.
Find your account details:
If the query fails, open the account selector in Snowsight and select View account details. Copy the Account/Server URL instead.

Request the integration

Send these details or your Account/Server URL through the Support Center: Historical activity events are not included. Kadoa confirms availability for your region. Accounts in Kadoa’s region use a direct share. Other regions or clouds require a private listing.

Import the share

For a direct share, complete these steps:
1

Find the share

In Snowsight, open Data sharing > External sharing > Shared with you. Under Ready to Get, select the share whose name starts with KADOA_SHARE_.
2

Create a database

Enter a database name such as KADOA. Choose the roles that can query it. Select Get Data.
3

Send the verification code

In your new database, find the schema whose name starts with TEAM_. Replace <KADOA_SCHEMA> with that schema name. If you chose another database name, replace KADOA too:
Send the returned code to Support. Kadoa then publishes data to the same database and schema.
For a private listing, open Shared with you > Privately shared listings. Select the listing whose name starts with KADOA_LISTING_. Complete the listing import steps. Support provides the verification instructions for your listing.

Verify the first delivery

Allow about 5 minutes after a workflow run completes. Select your warehouse, database, and Kadoa schema in Snowsight. Find the delivered run and its data view:
Use the returned view_name and job_id to count that run’s rows:
Confirm that job_id and the row count match the same run in the Kadoa dashboard.

Query the shared views

Get exact view names from WORKFLOW_SCHEMA_VERSIONS. Do not substitute a workflow ID into a view name. Each data view can contain multiple runs. Filter by job_id to query one run. Versioned views keep their schema when a new version appears. Optional views include ACTIVITY_LOG and TPL_<GENERATED_ID>__LATEST for template data.

Load cloud storage exports with Snowpipe

You can also load files from Amazon S3 or Google Cloud Storage with a Snowpipe you manage. This option uses bucket delivery instead of the native Snowflake share.
  1. Complete a workflow run so a sample data file exists.
  2. Limit the pipe to one workflow’s path and one format, such as Parquet. Exclude other formats and workflow health files.
  3. Configure storage access and automatic loading with Snowflake’s S3 guide or GCS guide.
See file paths for the default layout. If Kadoa hosts your S3 bucket, send Support the pipe’s notification_channel value to configure event notifications.

What’s next

Amazon S3

Set up bucket delivery.

Databricks

Use Delta Sharing.

How data integrations work

See delivery timing, formats, and file paths.