SNOWFLAKE n8n INTEGRATION: AUTOMATE SNOWFLAKE WITH N8N

The Execute Query action is your most flexible tool in the Snowflake n8n integration. It allows you to run any valid SQL statement against your Snowflake database, giving you complete control over data retrieval, manipulation, and analysis directly within your automation workflows.

Key parameters:

• Credential to connect with: A required dropdown field where you select your pre-configured Snowflake account credentials. This determines which database and warehouse the query will execute against.
• Operation: A required dropdown set to "Execute Query" for this action. This tells n8n you want to run a custom SQL statement rather than a predefined operation.
• Query: A required multi-line text input field where you enter your SQL statement. This field supports both static queries and dynamic expressions, allowing you to inject data from previous nodes into your query.

Use cases:

• Run SELECT statements to retrieve customer segments for email campaigns
• Execute aggregation queries to calculate daily metrics triggered by a schedule
• Perform complex JOINs across multiple tables to prepare data for downstream processing
• Run DELETE or TRUNCATE commands as part of data cleanup workflows

This action is particularly powerful when combined with n8n's expression syntax. You can dynamically build queries using data from previous nodes—for example, constructing a WHERE clause based on a customer ID received from a webhook.

The Insert action enables you to add new records to your Snowflake tables automatically. This is essential for data ingestion workflows where information from external sources needs to flow into your data warehouse in real-time.

Key parameters:

• Credential to connect with: Required dropdown to select your Snowflake authentication credentials.
• Operation: Set to "Insert" to add new records to a table.
• Table: A required text input field specifying the target table name. This field supports both "Fixed" mode for static table names and "Expression" mode for dynamic table selection based on workflow data.
• Columns: A text input field where you list the column names that will receive data, separated by commas. In the example configuration, "id,name,description" indicates data will be inserted into these three columns.

Use cases:

• Automatically insert new leads from web forms into a prospects table
• Sync new e-commerce orders from Shopify into Snowflake for analytics
• Archive processed data from temporary staging tables
• Log automation events for audit and debugging purposes

💡 TIP: Make sure your column order in the "Columns" parameter matches the data structure coming from previous nodes. Mismatched columns are a common source of insert failures.

The Update action allows you to modify existing records in your Snowflake tables based on a matching key. This is crucial for maintaining data accuracy across your systems and keeping your warehouse synchronized with source applications.

Key parameters:

• Credential to connect with: Required dropdown for selecting your Snowflake account credentials.
• Operation: Set to "Update" to modify existing records rather than insert new ones.
• Table: Required text input specifying which table contains the records you want to update.
• Update Key: A required text input field that defines which column(s) identify the records to update. In the screenshot, "id" is specified, meaning n8n will match incoming data against the id column to find the correct rows.
• Columns: Required text input listing which columns should receive new values. The example shows "name,description", indicating only these fields will be modified—other columns remain untouched.

Use cases:

• Update customer information when CRM records change
• Sync inventory levels from your e-commerce platform
• Modify order statuses as they progress through fulfillment stages
• Refresh calculated fields when source data changes

The Update Key parameter is critical for accuracy. Always use a unique identifier column (like a primary key or composite key) to ensure updates target the correct records. Using non-unique columns could result in unintended mass updates.