Skip to Content

Turn your connections into holiday cash with our new Customer Referral Program! Learn more

✕

Snowflake connector for Jitterbit Integration Studio

Summary

The Snowflake connector establishes access to Snowflake.

The Snowflake connector provides an interface for creating a Snowflake connection, the foundation used for generating instances of Snowflake activities. These activities, once configured, interact with Snowflake through the connection.

The Snowflake connector is accessed from the design component palette's Project endpoints and connectors tab (see Design component palette).

Connector overview

This connector is used to first configure a Snowflake connection. Activity types associated with that connection are then used to create instances of activities that are intended to be used as sources (to provide data in an operation) or targets (to consume data in an operation).

Together, a specific Snowflake connection and its activities are referred to as a Snowflake endpoint:

Snowflake activity types

  • Get: Retrieves a CSV file of table or view data from Snowflake and is intended to be used as a source in an operation.

  • Query: Retrieves a CSV file of table or view data from Snowflake and is intended to be used as a source in an operation.

  • Merge: Inserts or updates a CSV file of table data into Snowflake and is intended to be used as a target in an operation.

  • Invoke Stored Procedure: Invokes a stored procedure created in Snowflake and is intended to be used as a target in an operation.

  • Update: Updates table data in Snowflake and is intended to be used as a target in an operation.

  • Delete: Deletes table data and view data from Snowflake and is intended to be used as a target in an operation.

  • Insert: Inserts table data (either as a CSV file or directly mapped to columns of a table) into Snowflake and is intended to be used as a target in an operation.

Note

This connector is a Connector SDK-based connector, which may be referred to by Jitterbit when communicating changes made to connectors built with the Connector SDK.

Prerequisites and supported API versions

The Snowflake connector requires the use of an agent version 10.1 or later. These agent versions automatically download the latest version of the connector when required.

The Snowflake connector uses version 3.19.0 of the Snowflake JDBC Driver, and the Snowflake SQL commands. Refer to the API documentation for information on the schema nodes and fields.

The Snowflake connector currently requires password-based authentication.

Snowflake user TYPE property must be set to LEGACY_SERVICE and future deprecation of single-factor authentication

Snowflake has announced the upcoming deprecation of single-factor authentication, which affects integrations that connect to Snowflake using a password. As the Integration Studio Snowflake connector currently requires password-based authentication, all users of the Snowflake connector are affected.

Recommended user action

User action is required in two phases:

  1. By March 31, 2025, the TYPE property of the user account you use to connect to Snowflake must be set to LEGACY_SERVICE in order to continue using password-based authentication (see Types of users). Without user action, existing integrations using Snowflake single-factor password authentication are expected to begin failing in April 2025.

  2. By November 2025, you must update the type of authentication used to connect to Snowflake to OAuth or key-pair authentication. At this time, password-based authentication will no longer be supported. In an upcoming release, the Integration Studio Snowflake connector will be updated to add support for the newly required authentication methods.

Troubleshooting

If you experience issues with the Snowflake connector, these troubleshooting steps are recommended:

  1. Click the Test button in the connection configuration to ensure the connection is successful and to ensure the latest version of the connector is downloaded to the agent (unless using the Disable Auto Connector Update organization policy).

    Note

    Snowflake Developer Instances are known to "go to sleep" if you haven't recently logged in to the Snowflake UI or used the instance. If a table does not populate with available objects, first ensure that the Snowflake instance is active, and then ensure you are connected to it by reopening the Snowflake connection and retesting the credentials.

  2. Check the operation logs for any information written during execution of the operation.

  3. Enable operation debug logging (for cloud agents or for private agents) to generate additional log files and data.

  4. If using private agents, you can check the agent logs for more information.

  5. For additional troubleshooting considerations, see Operation troubleshooting.