maestro-automate
latest
false
Maestro Automate user guide
- Get started
- Build
- HTTP Request
- How connector nodes work
- Create a connection
- Sales and customer relationships
- Customer support and help desk
- Messaging and meetings
- Email
- Marketing
- Social media
- Files, documents, and e-signature
- Projects, collaboration, and code
- People and recruiting
- Finance and commerce
- AI models and agents
- Speech, vision, and language
- Data and location
- Cloud, identity, and security
- Deploy and run
- Examples
- Reference
Snowflake
Look up the Snowflake connector: its actions and events in alphabetical order, and the sign-in methods of a Snowflake connection.
The Snowflake connector lets a workflow query and manage data in a Snowflake data warehouse. In the Add node panel, it's in the Connector category, under Snowflake. How connector nodes work describes how a connector node is set up.
This page lists what the connector can do in Maestro Automate. Select an action or event to see how to configure it.
Actions
Each action is a node that does one thing in Snowflake.
| Action | What it does |
|---|---|
| Delete Record | Deletes a record in Snowflake. |
| Execute Any Query Asynchronously | Execute queries asynchronously in Snowflake, including select, insert, update, and stored procedures. |
| Execute Select Query Synchronously | Executes a SELECT query on a Snowflake warehouse and returns the result set synchronously. |
| Get Asynchronous Query Results | Retrieves the result set for a previously executed asynchronous Snowflake query using its Query ID. |
| Get Asynchronous Query Status | Retrieves the status of an asynchronous Snowflake query using its Query ID. |
| Get Record | Retrieves a record in Snowflake. |
| Insert Record | Insert a new record in Snowflake. |
| List Records | List records in Snowflake. |
| Replace Record | Replace a record in Snowflake. |
Events
Each event can start a workflow, as a Connector trigger, or pause a run until it happens, as a Connector event. In the connector's list, events have the WAIT tag.
| Event | What it does |
|---|---|
| Asynchronous Query Status Changed | Triggers when a Snowflake asynchronous query reaches a specified execution status. |
| Record Created | Trigger when a new record is added in Snowflake. |
| Record Updated | Trigger when a record is updated in Snowflake. |
Connection
A Snowflake node signs in through a connection. Create a connection describes how to create one from the node. On the Connect to page, you sign in with this method:
| Sign-in method | What you need |
|---|---|
| OAuth 2.0 | OAuth 2.0 Authorization code Snowflake OAuth authorization flow: + Client ID + Client secret + Database host + Warehouse + Database schema name + Database name + Role; OAuth 2.0 Client Credentials with Microsoft Entra ID (Snowflake External OAuth with Microsoft Entra ID): + Database host - your Snowflake hostname URL, for example https://hostname.snowflakecomputing.com + Warehouse - the Snowflake warehouse that processes queries + Database name + Database schema name - optional. If left empty, PUBLIC is used. + Client ID - the Application (client) ID from the Overview section of your Microsoft Entra ID application registration + Client secret - from the Certificates & secrets section of your Microsoft Entra ID application registration + Tenant ID - the Directory (tenant) ID from the Overview section of your Microsoft Entra ID application registration + Scope - the Application ID URI of the Microsoft Entra ID resource application representing Snowflake, suffixed with /.default, for example api://<application-id-uri>/.default + Role - optional. Must be an existing role granted to the Snowflake user mapped to the Microsoft Entra ID service principal. Leave blank to use the user's default role; External OAuth 2.0 Authorization Code with PKCE (External OAuth overview): + Database host - your Snowflake hostname URL, for example https://hostname.snowflakecomputing.com + Warehouse + Database name + Database schema name - optional. If left empty, PUBLIC is used. + Authorization URL, Token URL, and Refresh token URL - the OAuth 2.0 endpoints of your identity provider + Client ID - from the application registration in your identity provider. This method uses a public client, so no client secret is required. + Scope - offline_access is always included, because the connection needs it to refresh its token. Add the scopes your identity provider requires for Snowflake. + Role - optional. Must be an existing role granted to the Snowflake user that the token maps to. Leave blank to use the user's default role; RSA (Key Pair Authentication & Key Pair Rotation) + Database host + Username + RSA private key + Warehouse + Database schema name + Database name + Programmatic Access Token (Using programmatic access tokens for authentication) + Username + Programmatic Access Token + Warehouse + Database Schema Name + Database Name + Role; To authenticate using RSA, you must use an unencrypted RSA private key; Connections via AWS PrivateLink are not supported; Irrespective of the selected authentication method, if your Snowflake instance restricts access by IP, you must configure an allow list for the IPs used by Integration Service. For details, refer to Configuring the firewall in the Automation Cloud Admin guide. Because the IP range migration is ongoing, see the deprecation notice at the beginning of the legacy page for more information; The Snowflake connector does not support Relay (private connections). Relay supports only HTTP-based connections, and this connector uses the Snowflake JDBC driver. |
Snowflake authentication in the Integration Service guide describes the full connection setup, including prerequisites and advanced settings.
Next steps
- Connector: every connector, grouped by area.
- Create a connection: sign a workflow in to an app.
- Community: ask questions and share workflows with other builders on the UiPath Forum.