Snowflake Connector Reference

Snowflake is a fully managed, cloud-based data warehouse solution that operates under a Software as a Service (SaaS) business model. This allows clients to store data and run analytics without the need for an on-premise solution.

For more information about privileges for triggers and actions, refer to Overview of Access Control.

Connections

To connect to a system, whether it is a source of data or the target where you are sending data, you must create a connection with that system’s required credentials. You typically connect to different systems within a flow and can reuse each connection every time you need to connect.

This system requires the following credential information for its connections:

Connection Name: Enter a connection name that will help you remember the details of this connection. You can reuse connections multiple times in a single flow, and in more than one flow, and the credentials are hidden after you create the connection. Therefore, it’s helpful to provide a name that easily identifies this connection from others.

Only you can see the connection. Other users in your Composer app must create their own connections.
Username and password: The username and password that you used to log in to Snowflake.
Account Name: The account name that is provided when registering for the Snowflake account. The account name is in the <OrgId>-<AccountId> format.
Warehouse: The name of the Snowflake warehouse to use.
Database: The Snowflake database to which you want to connect.
Schema: The Snowflake database schema to use.

Data Types

The following data types are supported by Snowflake Connector:

INT
NUMBER
DECIMAL
BIGINT
TINYINT
NUMERIC
INTEGER
BYTEINT
FLOAT
FLOAT4
FLOAT8
DOUBLE
REAL
VARCHAR
CHAR
CHARACTER
STRING
TEXT
BOOLEAN
DATE
DATETIME
TIMESTAMP
TIMESTAMP_NTZ

Triggers

Each flow starts with either a scheduler or a trigger. Schedulers are set to a default frequency of 15 minutes. Triggers, such as "each time a new record is created", are defined by you and provide multiple options related to the data in your system.

Triggers use a polling process to actively check for new updates from an external system. The polling frequency is 15 seconds.

This system provides the following trigger options:

On New Row

Returns all new rows of a table based on the highest watermark value every 15 seconds.

If the watermark value of a new row is lower than the highest watermark value, the new row is discarded. If the watermark value of a new row is higher than the highest watermark value, the new row is picked up and the watermark is set to the new highest value.

If the flow is deactivated and reactivated manually, the watermark resets to the start time of the flow. If a start time is not specified in the flow, Composer uses the time the flow is activated as the timestamp.

Provide a value for the following fields:

Table: Note that this trigger supports views within the Table field.
Created date column: The following column data types are available for this field:
- DATE
- DATETIME
- TIMESTAMP
- TIMESTAMP_NTZ

On New Or Updated Row

Returns all new or updated rows of a table based on the highest watermark value between Created date column and Last modified date column every 15 seconds.

If the watermark value of a new or updated row is lower than the highest watermark value, the new or updated row is discarded. If the watermark value of a new or updated row is higher than the highest watermark value, the new or updated row is picked up and the watermark is set to the new highest value.

Provide a value for the following fields:

Table: Note that this trigger supports views within the Table field.
Created date column: The following column data types are available for this field:
- DATE
- DATETIME
- TIMESTAMP
- TIMESTAMP_NTZ
Last modified date column: The following column data types are available for this field:
- DATE
- DATETIME
- TIMESTAMP
- TIMESTAMP_NTZ

Polling Frequency

For triggers in this connector, the Polling Frequency field is required. This field enables you to select how often Composer makes a request to the underling system API to look for changes to records in active flows. You can select a different polling frequency for each flow in your organization. With a shorter frequency, the flow executes more often; however, a shorter frequency consumes more API calls. For example, if you have an order management flow, you might require nearly real-time updates, which can be achieved with a 15-second polling interval (which equates to 5760 API calls per day). In contrast, if your flow updates a pricing catalog, you could poll the flow every hour (which equates to 24 API calls per day).

Actions

After you connect to a system and define the trigger or configure a scheduler, you define the actions that the flow performs. For example, you can copy a record between different systems, such as Workday and Salesforce. The actions you can perform depend on which system you are connected to.

This system provides the following actions:

Insert Rows: Updates a table by inserting one or more rows into the table. Provide a value for Query.
Update Rows: Updates a set of rows. Provide a value for Query.
Delete Rows: Deletes a set of rows. Provide a value for Query.
Select Rows: Retrieves a set of rows. Provide a value for Query.