Snowflake

Overview

Birdie using read-only access:

• Integration via Reader Account (Snowflake Data Sharing) – recommended for shared-data environments

• Integration via Direct OAuth Connection – recommended when Birdie connects directly to your main Snowflake account

Birdie can import data from Snowflake into Birdie for analytics, enrichment and reporting purposes, including:

• Customers and accounts

• Operational and reference tables

• Feedback-related datasets exposed by the client

Because each Snowflake installation is unique, Birdie’s team will work with your IT administrators to finalize details. This article explains how your Snowflake admin can generate and provide the credentials needed to enable the integration.

Birdie connects to a Snowflake Reader Account created via Snowflake Data Sharing. Birdie runs SELECT queries against databases instantiated from shared objects in that reader account.This model is common when:

• Your organization already uses provider to consumer data sharing

• You want strict isolation between your production Snowflake account and external consumers such as Birdie

Schema requirements

All Birdie database connectors (Snowflake, Databricks, BigQuery, etc.) require one table or view per feedback type, following the Birdie schema definition. Examples of feedback types:

• nps

• csat

• review

• social_media_post

• support_ticket

Each feedback type must exist as:

• A table, or

• A view

Birdie provides the detailed schema reference separately (same model as the S3 schema documentation).

Reader Account method

Overview

Birdie connects to a Snowflake Reader Account created via Snowflake Data Sharing. Birdie runs SELECT queries against databases instantiated from shared objects in that reader account.This model is common when:

• Your organization already uses provider to consumer data sharing

• You want strict isolation between your production Snowflake account and external consumers such as Birdie

Requirements

Before starting:

• Your account supports provider data sharing

• You have ACCOUNTADMIN (or equivalent) access on the reader account

• The provider account already exposes the necessary shares with the data Birdie will use

Setup in Snowflake

1

Log into the Reader Account

Use SnowSQL, the Snowflake Web UI, or another supported client:

Set a role

USE ROLE ACCOUNTADMIN;

2

(Optional) Create a dedicated role for Birdie

Create a dedicated role

CREATE ROLE BIRDIE_READ;

3

Create the Birdie user inside the reader account

Create user

CREATE USER BIRDIE_USER
  PASSWORD = '<STRONG_PASSWORD>'
  DEFAULT_ROLE = BIRDIE_READ
  MUST_CHANGE_PASSWORD = FALSE;

Grant user

GRANT ROLE BIRDIE_READ TO USER BIRDIE_USER;

4

(Optional) Create a resource monitor

Create monitor

CREATE RESOURCE MONITOR BIRDIE_MONITOR WITH CREDIT_QUOTA = 1000;
ALTER WAREHOUSE BIRDIE_WH SET RESOURCE_MONITOR = BIRDIE_MONITOR;

You can adapt the name and quota as needed.

5

Create a virtual warehouse in the reader account

Create warehouse

CREATE WAREHOUSE BIRDIE_WH
  WAREHOUSE_SIZE = SMALL
  AUTO_SUSPEND = 60
  AUTO_RESUME = TRUE;

6

Instantiate databases from provider shares

Create shares

CREATE DATABASE SHARED_DB_1 FROM SHARE <PROVIDER_ACCOUNT>.<SHARE_NAME_1>;
CREATE DATABASE SHARED_DB_2 FROM SHARE <PROVIDER_ACCOUNT>.<SHARE_NAME_2>;

7

Grant privileges to the Birdie role

Warehouse usage:

Grant role

GRANT USAGE ON WAREHOUSE BIRDIE_WH TO ROLE BIRDIE_READ;

Imported privileges on shared databases

Grant role

GRANT IMPORTED PRIVILEGES ON DATABASE SHARED_DB_1 TO ROLE BIRDIE_READ;
GRANT IMPORTED PRIVILEGES ON DATABASE SHARED_DB_2 TO ROLE BIRDIE_READ;

8

Share Reader Account credentials securely with Birdie

Provide to Birdie:

• Reader account identifier (host)

• Username: BIRDIE_USER

• Role: BIRDIE_READ

• Warehouse: BIRDIE_WH

• Database and schema names that contain the shared data

• Password or password rotation mechanism

Birdie will configure the Snowflake connector using these details and run validation queries from the reader account.

Integration via Direct OAuth Connection

Overview

In this model, Birdie connects directly to your main Snowflake account using OAuth instead of static passwords. This is recommended when:

• You prefer SSO or OAuth-based access

• You do not use Snowflake Data Sharing

• You want Birdie to access native production schemas directly

Requirements

• ACCOUNTADMIN (or equivalent) privileges in the main Snowflake account

• Access to the Snowflake web console or CLI

• The Snowflake connector has been enabled on the Birdie side

Setup in Snowflake

1

Create the OAuth Security Integration

Create an integration

CREATE SECURITY INTEGRATION BIRDIE_OAUTH_INTEGRATION
   TYPE = OAUTH
   ENABLED = TRUE
   OAUTH_CLIENT = CUSTOM
   OAUTH_CLIENT_TYPE = 'CONFIDENTIAL'
   OAUTH_REDIRECT_URI = 'https://api.birdie.ai/oauth/callback'
   OAUTH_ISSUE_REFRESH_TOKENS = TRUE
   OAUTH_REFRESH_TOKEN_VALIDITY = 7776000;

Verify

DESC SECURITY INTEGRATION BIRDIE_OAUTH_INTEGRATION;

2

Create a role and user for Birdie

Create role

CREATE ROLE BIRDIE_READ;

Grant role

GRANT USAGE ON WAREHOUSE <WAREHOUSE_NAME> TO ROLE BIRDIE_READ;
GRANT USAGE ON DATABASE <DATABASE_NAME> TO ROLE BIRDIE_READ;
GRANT USAGE ON SCHEMA <SCHEMA_NAME> TO ROLE BIRDIE_READ;
GRANT SELECT ON ALL TABLES IN SCHEMA <SCHEMA_NAME> TO ROLE BIRDIE_READ;

Create user

CREATE USER BIRDIE_INTEGRATION_USER
  PASSWORD = '<SECURE_PASSWORD>'
  DEFAULT_ROLE = BIRDIE_READ
  MUST_CHANGE_PASSWORD = FALSE;

Grant role

GRANT ROLE BIRDIE_READ TO USER BIRDIE_INTEGRATION_USER;

3

Generate and test an OAuth token

Example using SnowSQL

snowsql
  -a <ACCOUNT_IDENTIFIER>
  -u BIRDIE_INTEGRATION_USER
  -o authenticator=oauth
  -o oauthAccessToken="<ACCESS_TOKEN>"
  -r BIRDIE_READ
  -w <WAREHOUSE_NAME>
  -d <DATABASE_NAME>
  -s <SCHEMA_NAME>

4

Share OAuth credentials securely with Birdie

Provide:

• Host: Account identifier (e.g. <ACCOUNT_IDENTIFIER>.snowflakecomputing.com)

• User name (e.g. BIRDIE_INTEGRATION_USER)

• Password: The password set for the Birdie user in step 2

• OAuth Client ID: From the security integration created in step 1

• OAuth Client Secret: From the security integration created in step 1

• Role (e.g. BIRDIE_READ)

• Warehouse (e.g. BIRDIE_WH)

• Database (e.g. <DATABASE_NAME>)

• Schema (e.g. <SCHEMA_NAME>)

Birdie uses the host, client ID, and client secret to reach the Snowflake OAuth token endpoint, and then the user name and password to complete the authorization code flow and obtain an access token.

Birdie will configure the connector and confirm once the integration is active.

Security notes

• Birdie never requires admin privileges for day-to-day operations

• Access granted to Birdie is read-only, unless a specific export pipeline is explicitly configured

• All credentials must be shared via a secure channel

• OAuth is preferred over static passwords whenever possible

Data in scope

Once enabled, the Snowflake connector can import data from Snowflake into Birdie (for example, customer, account, or operational tables you expose to the Birdie role) and export Birdie data such as feedback records, areas, opportunities, and metrics back into Snowflake.

References

• ​Snowflake Data Sharing

• ​Snowflake Security and Roles

• ​Snowflake OAuth