Snowflake

​

Introduction

Qobra connects to Snowflake with basic authentication, username / password credentials.

The integration is used to synchronize exposed tables, their columns and their content. This integration is readonly and does not write anything in your Snowflake database.

​

Setup

1. Create an account to setup the Qobra connection, ensuring the principle of least privilege. This means the account needs to have read only access, on table that need to be synchronized with Qobra.

   You’ll find Snowflake’s documentation regarding User, role, & privilege commands here.

   Once your account is created, make sure you keep its username and password for later steps.

2. Whitelist Qobra’s IP: 13.39.2.144

3. You’ll then be able to fill in connection modal in app:

   • Username: Snowflake account username
   • Password: Snowflake account password
   • Host: Snowflake account’s unique URL
   • Port: by default 443 for encrypted (TLS/SSL) connections
   • Database: Snowflake database

​

Synchronization

​

Table requirements

To synchronize a file to Qobra, it must meet requirements:

• the file contains a unique identifier column
• the file contains a name column
• the user values contained in the file must be emails by default, but it can be changed in app at table creation

​

Total synchronization

This integrations does total synchronization, meaning the whole document will be synced at every refresh.

​

Refresh schedule

You can edit this integration synchronization periods in application, to better suit your needs.

​

Supported types

You’ll find below the fields types supported by the Qobra integration, and their mapping to Qobra types.

Snowflake type	Qobra type
TEXT	string, picklist, multipicklist, user
NUMBER	number, amount, percentage, user
FLOAT	number, amount, percentage
DATE	date
TIMESTAMP_TZ	date

​

Custom querying

With this integration, you can apply a custom query to your table synchronization, to avoid synchronizing too much information, consequently making synchronization quicker.

Custom queries are based on SQL where conditions. For instance, you could add as a custom query StageName = 'Closed Won’ to filter your Opportunity object.

Contact support for more information.