How to use IBM App Connect with Snowflake
Snowflake is a fully managed SaaS (software as a service) solution that provides a single platform for data warehousing, data lakes, data engineering, data science, data application development, and secure sharing and consumption of real-time or shared data.
- App Connect Enterprise as a Service connector
-
Local
connector in containers (Continuous Delivery release) 12.0.7.0-r3 or later -
Local connector in containers (Long Term Support Cycle-2 release)
Connecting to Snowflake
Complete the connection fields that you see in the App Connect Designer page (previously the Catalog page) or flow editor. If necessary, work with your Snowflake administrator to obtain these values.
Snowflake authorization types and connection fields:
- BASIC OAUTH
-
Important: The BASIC OAUTH authentication type is scheduled for deprecation in February 2026.
-
Endpoint URL:
The account identifier for an account in your organization. This value forms part of the account URL (
https://<account_identifier>.snowflakecomputing.com) that you use to log in to your Snowflake account.- Preferred format: Specify the account identifier in the format
<orgname>-<account_name>, where:- <orgname> is the name of your Snowflake organization.
- <account_name> is a unique account name in the organization.
Example:
myorg-account123 - Legacy format: Specify the account identifier in the format
<account_locator>.<cloud_region_id>or<account_locator>.<cloud_region_id>.<cloud>, where:- <account_locator> is a Snowflake-assigned locator, which is an alias for your account name.
- <cloud_region_id> is a cloud region identifier.
- <cloud> is a cloud platform identifier.
Example:
ab12345.us-east-2.aws
You can view the account identifier in the Snowflake web interface by clicking .
For more information, see Account Identifiers and Connecting with a URL in the Snowflake documentation.
- Preferred format: Specify the account identifier in the format
- MLTS
-
Endpoint URL:
The account identifier for an account in your organization. This value forms part of the account URL (
https://<account_identifier>.snowflakecomputing.com) that you use to log in to your Snowflake account.- Preferred format: Specify the account identifier in the format
<orgname>-<account_name>, where:- <orgname> is the name of your Snowflake organization.
- <account_name> is a unique account name in the organization.
Example:
myorg-account123 - Legacy format: Specify the account identifier in the format
<account_locator>.<cloud_region_id>or<account_locator>.<cloud_region_id>.<cloud>, where:- <account_locator> is a Snowflake-assigned locator, which is an alias for your account name.
- <cloud_region_id> is a cloud region identifier.
- <cloud> is a cloud platform identifier.
Example:
ab12345.us-east-2.aws
You can view the account identifier in the Snowflake web interface by clicking .
For more information, see Account Identifiers and Connecting with a URL in the Snowflake documentation.
- Preferred format: Specify the account identifier in the format
To obtain the connection values for Snowflake and to connect to App Connect, see Obtaining connection values for Snowflake.
To connect to a Snowflake endpoint from the App Connect Designer Applications and APIs page for the first time, expand Snowflake, then click Connect. For more information, see Managing accounts.
Before you use the account that is created in App Connect in a flow, rename the account to something meaningful that helps you to identify it. To rename the account on the Applications and APIs page, select the account, open its options menu (⋮), then click Rename Account.
General considerations
Before you use App Connect Designer with Snowflake, take note of the following considerations:
- (General consideration) You can see lists of the trigger events and
actions that are available on the Applications and APIs page of the App Connect Designer.
For some applications, the events and actions depend on the environment and whether the connector supports configurable events and dynamic discovery of actions. If the application supports configurable events, you see a Show more configurable events link under the events list. If the application supports dynamic discovery of actions, you see a Show more link under the actions list.
- (General consideration) If you are using multiple accounts for an application, the set of fields that is displayed when you select an action for that application can vary for different accounts. In the flow editor, some applications always provide a curated set of static fields for an action. Other applications use dynamic discovery to retrieve the set of fields that are configured on the instance that you are connected to. For example, if you have two accounts for two instances of an application, the first account might use settings that are ready for immediate use. However, the second account might be configured with extra custom fields.
Events and actions
Snowflake events
These events are for changes in this application that trigger a flow to start completing the actions in the flow.
Snowflake actions
Your flow completes these actions on this application.
| Object | Action | Description |
|---|---|---|
| Custom SQL queries | Execute custom SQL query | Creates and executes a custom SQL statement under the selected database and schema |
| Pipes | Create pipe | Creates a new pipe in the system for defining the COPY INTO <table>statement used by Snowpipe to load data from an ingestion queue into tables |
| Retrieve pipes | Retrieve pipe for the respective database in the Snowflake account | |
| Rows | Create row | Create a row in the respective database in your Snowflake account |
| Delete row | Delete a row from the respective database in your Snowflake account | |
| Retrieve rows | Retrieve a row from the respective database in your Snowflake account | |
| Update row | Update a row for the respective database in your Snowflake account | |
| Stages | Create stage | Creates a newly named stage to use for loading data from files into Snowflake tables and unloading data from tables into files |
| Retrieve stages | Retrieve stages by schema name from a Snowflake account database | |
| Stored procedures | Call stored procedure | Call a stored procedure under a specific Snowflake database and schema |
| Create stored procedure | Creates a new stored procedure | |
| Tables | Copy data into table | Copy data from a staged file into a table in a Snowflake database |
| Copy from table into location | Copy data from a table in Snowflake to an external storage location | |
| Copy into table with transformation | Copy data from a staged file into a table using transformation | |
| Tasks | Create task | Creates a new named external stage to use for loading data from files into Snowflake tables and unloading data from tables into files |
| Update task status | Update or alter task status to either resume or suspend |
Examples
Use templates to quickly create flows for Snowflake
Learn how to use App Connect templates to quickly create flows that perform actions on Snowflake. For example, open Discover, and then search for Snowflake.
Use IBM® App Connect to build flows that integrate with Snowflake.
Read the blog in the IBM Community to learn how to insert data into the Snowflake table when a new file gets created in Amazon S3. Click Read the blog to go to the blog.