- 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 Cortex
Look up the Snowflake Cortex connector: its actions in alphabetical order, and the sign-in methods of a Snowflake Cortex connection.
The Snowflake Cortex connector lets a workflow interact with Snowflake Cortex agents. In the Add node panel, it's in the Connector category, under Snowflake Cortex. 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 to see how to configure it.
Actions
Each action is a node that does one thing in Snowflake Cortex.
| Action | What it does |
|---|---|
| Interact Agent | Sends a user query to the Cortex Agent object and returns its response as a stream of events. |
| Run Agent Without an Agent Object | Interacts with the agent without creating an agent object. |
Connection
A Snowflake Cortex node signs in through a connection. Create a connection describes how to create one from the node. On the Connect to page, choose one of these sign-in methods:
| Sign-in method | What you need |
|---|---|
| Programmatic Access Token | * Account Identifier * Personal Access Token. |
| OAuth 2.0 Authorization code | * Account Identifier * Client ID * Client Secret * Scope - Defaults to session:role:SYSADMIN. You can change this to a different role, provided that role is granted to the connecting user. |
| OAuth 2.0 Client Credentials with Microsoft Entra ID | * Account Identifier * Client ID and Client Secret - From the Microsoft Entra ID application registration. * Scope - The scope of the Microsoft Entra ID application representing Snowflake, in the form api://<application-id-uri>/.default. * Tenant ID - The Microsoft Entra ID directory (tenant) ID, available in the Overview section of your Microsoft Entra ID application registration. |
| External OAuth 2.0 Authorization Code with PKCE | * Account Identifier * 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. |
Snowflake Cortex 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.