Snowflake connection in Jitterbit Studio

Introduction

A Snowflake connection, created using the Snowflake connector, establishes access to Snowflake. Once a connection is configured, you can create instances of Snowflake activities associated with that connection to be used either as sources (to provide data in an operation) or as targets (to consume data in an operation).

Create or edit a Snowflake connection

A new Snowflake connection is created using the Snowflake connector from one of these locations:

• The design component palette's Project endpoints and connectors tab (see Design component palette).
• The Global Endpoints page (see Create a global endpoint in Global Endpoints).

An existing Snowflake connection can be edited from these locations:

• The design component palette's Project endpoints and connectors tab (see Design component palette).
• The project pane's Components tab (see Component actions menu in Project pane Components tab).
• The Global Endpoints page (see Edit a global endpoint in Global Endpoints).

Configure a Snowflake connection

Each user interface element of the Snowflake connection configuration screen is described below.

• Connection name: Enter a name to use to identify the connection. The name must be unique for each Snowflake connection and must not contain forward slashes / or colons :. This name is also used to identify the Snowflake endpoint, which refers to both a specific connection and its activities.

• Authentication: Select the authentication type, one of Key-Pair, OAuth, or Password (Deprecated):

  • Key-Pair: Select this option to use a key-pair for authentication:

    • Host name: Enter the Snowflake host name. This is the Snowflake account name (such as example-account123) and the Snowflake domain name of snowflakecomputing.com concatenated together, such as example-account123.snowflakecomputing.com.

    • User name: Enter the Snowflake username.

    • Private key specification: Select either Unencrypted or Encrypted key to identify the type of private key used.

    • Private key: Enter the private key. For more information, refer to the Snowflake Key-pair authentication and key-pair rotation documentation.

    • Passphrase: If Encrypted key is selected for Private key specification, enter the passphrase associated with the encrypted private key.

  • OAuth: Select this option to use 3-legged OAuth 2.0 for authentication. For important notes on access token and refresh token behavior, see Important notes.

    • Host name: Enter the Snowflake host name. This is the Snowflake account name (such as example-account123) and the Snowflake domain name of snowflakecomputing.com concatenated together, such as example-account123.snowflakecomputing.com.

    • User name: Enter the Snowflake username.

    • OAuth application: Select a Snowflake connector application configured in the Management Console App Registrations page. For more information on configuring a Snowflake connector application in the App Registrations page, refer to the Snowflake 3-legged OAuth prerequisites.

    • Log in with Snowflake: Click to authenticate through Snowflake in a separate browser tab and provide consent for Jitterbit to access the Snowflake application.

  • Password (Deprecated): Select this option to use a password for authentication:

    • Host name: Enter the Snowflake host name. This is the Snowflake account name (such as example-account123) and the Snowflake domain name of snowflakecomputing.com concatenated together, such as example-account123.snowflakecomputing.com.

    • User name and Password: Enter the Snowflake username and password.

      Snowflake is deprecating single-factor password authentication

      Snowflake is phasing out single-factor password authentication for all users, including the LEGACY_SERVICE-type service accounts required for this Password (Deprecated) authentication type. The rollout is enforced in phases:

      • Between May and July 2026, no new LEGACY_SERVICE accounts could be created; existing ones weren't yet affected.
      • Between August and October 2026, Snowflake migrates all remaining LEGACY_SERVICE accounts to TYPE=SERVICE on a rolling, per-account basis, notifying each account of its specific enforcement date within this window. Once migrated, a TYPE=SERVICE account can no longer authenticate with a password.

      If your Snowflake account is affected, connections using this authentication type fail. Update the connection to use OAuth or Key-Pair authentication instead, and configure the Snowflake user account to match.

• Account: Enter the Snowflake account name.

• Database name: Enter the Snowflake database name.

• Schema name: Enter the Snowflake schema name.

• Optional settings: Click to expand additional optional settings:

  • Role: Enter the Snowflake role. The available roles are GENERAL, PUBLIC, and READONLY.

  • Warehouse Name: Enter the Snowflake warehouse name.

  • Escape special characters: When selected, a single quote character (') is escaped (\') when it is present in an Insert or Invoke Stored Procedure activity's request payload.

    When unselected (default), and a single quote character (') is present in a request payload, a syntax error is returned at runtime.

  • Connection Custom Properties: Click the add icon to add a row to the associated table and enter a Key and Value for a custom property corresponding to a Snowflake JDBC connection parameter. By default, a row for JDBC_QUERY_RESULT_FORMAT is defined with a value of JSON.

    To save the row, click the submit icon in the rightmost column.

    To edit or delete a single row, hover over the rightmost column and use the edit icon or delete icon .

    To delete all rows, click Clear All.

• Use quote for Snowflake identifiers: Select this option to quote Snowflake identifiers such as table and column names in the SQL that the connector generates. Quoting preserves the case of an identifier instead of converting it to uppercase, which can cause an error, and allows identifiers that contain special characters such as a hyphen, which Snowflake rejects as invalid syntax when unquoted. By default this is selected.

• Test: Click to verify the connection using the provided configuration. When the connection is tested, the latest version of the connector is downloaded by the agent(s) in the agent group associated with the current environment. This connector supports suspending the download of the latest connector version by using the Disable Auto Connector Update organization policy.

• Save: Click to save and close the connection configuration.

• Discard changes: After making changes to a new or existing configuration, click to close the configuration without saving. A message asks you to confirm that you want to discard changes.

• Delete: After opening an existing connection configuration, click to permanently delete the connection from the project and close the configuration (see Component dependencies, deletion, and removal). A message asks you to confirm that you want to delete the connection.

Next steps

After a Snowflake connection has been created, you place an activity type on the design canvas to create activity instances to be used either as sources (to provide data in an operation) or as targets (to consume data in an operation).

Menu actions for a connection and its activity types are accessible from the project pane and design component palette. For details, see Actions menus in Connector basics.

These activity types are available:

• 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.

• Query v2: Retrieves a CSV file of table or view data across multiple Snowflake schemas 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.