Overview
Stigg’s integration with Snowflake serves a core principal of granting access to raw data, enabling the creation of customized reporting solutions and fostering informed business decision-making.Stigg’s native integration with Snowflake is included in the Scale plan, and is also available as an optional add-on to the Growth plan. See Stigg’s pricing for more details.
Available data types
Stigg’s integration with Snowflake allows you to sync the following Stigg entities to Snowflake:- Product catalog
- Products
- Plans
- Add-ons
- Features
- Customers
- Subscriptions
Stigg entity schema
Setting up the integration
Prerequisites
To setup the integration, a Snowflake account with the ACCOUNTADMIN role. If you don’t have an account with the ACCOUNTADMIN role, contact your Snowflake administrator to set one up for you.1
Generate Snowflake key pair
Stigg connects to Snowflake using key-pair authentication (password authentication is deprecated).
Follow the steps below to generate the private and public RSA key pair.
Follow the steps below to generate the private and public RSA key pair.
2
Create Stigg entities in Snowflake
In Snowflake, create the relevant Stigg entities (a role, user, warehouse, database and schema) with the OWNERSHIP permission.Open a new Snowflake worksheet and paste the below script:Replace Run the script, while using the “Run All” option (⌘ + Shift + Enter shortcut in Mac or CTRL + Shift + Enter in Windows).
<PASTE YOUR PUBLIC KEY HERE> with the base64 content of your rsa_key.pub file (without the header/footer lines).When pasting your public key into Snowflake, use only the Base64-encoded content of the key.
Do not include the
Incorrect formatting will prevent the connection from being established.
Do not include the
-----BEGIN PUBLIC KEY----- or -----END PUBLIC KEY----- lines, and ensure there are no extra spaces or line breaks.Incorrect formatting will prevent the connection from being established.
3
Grant Stigg access to your Snowflake cluster
By default, Snowflake allows users to connect to the service and internal stage from any computer or device. A security administrator (or higher) can use a network policy to allow or deny access to a request based on its origin.In this step we’ll ensure that Stigg has access to your Snowflake cluster.In Snowflake, open a new worksheet and run the below command:If the returned result is empty, all network access is allowed to your cluster, and specifically Stigg can access it - skip to the next section.If the returned result is not empty, an existing network policy is in place. To ensure that Stigg can access your cluster, update the existing policy and add Stigg’s IP addresses to the allowlist using the below command:
4
Connect Stigg with Snowflake
In Stigg, navigate to the Integrations > Apps > Snowflake section.Enter the below information in the opened form:
Click “Connect to Snowflake”.
| Field | Description |
|---|---|
| Account URL | The Snowflake account URL, for example: https://ab12345.us-east-2.aws.snowflakecomputing.com ![]() |
| Role | The role you specified when creating the Stigg entities in Snowflake, for example: STIGG_ROLE |
| Warehouse | The warehouse you specified when creating the Stigg entities in Snowflake, for example: STIGG_WAREHOUSE |
| Database | The database you specified when creating the Stigg entities in Snowflake, for example: STIGG_DATABASE |
| Schema | The schema you specified when creating the Stigg entities in Snowflake, for example: STIGG_SCHEMA |
| Username | The username you specified when creating the Stigg entities in Snowflake, for example: STIGG_USER |
| Private Key | The private key you created when generating key-pair |
| Passphrase (optional) | The passphrase protects your private key with an extra password. Snowflake recommends following PCI DSS guidelines and storing it securely. |
Migrating existing connections from password-based to key-pair authentication
If you previously connected Stigg to Snowflake using password-based authentication, you can easily migrate your connection to RSA key-pair authentication without losing access.1
Click Switch to key pair
In the Snowflake integration card, click Switch to key pair in the banner. This will open the guided migration wizard.

2
Generate your key pair
Follow the Generate Snowflake key pair above to create your private and public keys.
3
Update your Snowflake user
Use the script below to update the existing Stigg user and associate your new public key. This script removes password-based authentication and enables key-pair login.Replace
<BASE64_PUBLIC_KEY> with the base64 content of your public key (without the BEGIN/END lines).4
Update your Stigg connection
Go to connection details.
- Paste or upload your private key file (rsa_key.p8).
- Enter your passphrase (if applicable).
- Click Update Snowflake connection. Your integration will now use RSA key-pair authentication.
Existing data and sync configuration remain unchanged. Only the authentication method is updated.
Sync process and frequency
Upon completion of the integration setup, Stigg will perform a full sync of all of the available data types. Subsequent syncs will be incremental; thereby, significantly reducing the amount of data synchronized on a regular basis.Stigg syncs data to Snowflake on a daily basis at 12:00am UTC.

