- Getting started
- Notifications
- Licensing
- Troubleshooting
- Connector Builder
- Act! 365
- ActiveCampaign
- Active Directory - Preview
- Adobe Acrobat Sign
- Adobe PDF Services
- Amazon Bedrock
- Amazon Connect
- Amazon Polly
- Amazon SES
- Amazon Transcribe
- Amazon Web Services
- Anthropic Claude
- Asana
- AWeber
- Azure AI Document Intelligence
- Azure Defender for Cloud
- Azure Maps
- BambooHR
- Box
- Brevo
- Calendly
- Campaign Monitor
- Cisco Webex Teams
- Citrix Hypervisor
- Citrix ShareFile
- Clearbit
- Confluence Cloud
- Constant Contact
- Coupa
- CrewAI – Preview
- Customer.io
- Database Hub
- Databricks Agent
- Datadog
- DeepSeek
- Deputy
- Discord - Preview
- DocuSign
- Drip
- Dropbox
- Dropbox Business
- Egnyte
- Eventbrite
- Exchangerates
- Exchange Server - Preview
- Expensify
- Facebook
- Freshbooks
- Freshdesk
- Freshsales
- Freshservice
- GetResponse
- GitHub
- Gmail
- Google Cloud Platform
- Google Docs
- Google Drive
- Google Forms - Preview
- Google Maps
- Google Sheets
- Google Speech-to-Text
- Google Text-to-Speech
- Google Tasks - Preview
- Google Vertex
- Google Vision
- Google Workspace
- GoToWebinar
- Greenhouse
- Hootsuite
- HTTP
- HTTP Webhook
- Hubspot CRM
- HubSpot Marketing
- HyperV - Preview
- Icertis
- iContact
- Insightly CRM
- Intercom
- Jina.ai
- Jira
- Keap
- Klaviyo
- LinkedIn
- Mail
- Mailchimp
- Mailgun
- Mailjet
- MailerLite
- Marketo
- MCP - Preview
- Microsoft 365
- Microsoft Azure
- Microsoft Azure Active Directory
- Microsoft Azure AI Foundry
- Microsoft Azure OpenAI
- Microsoft Azure Sentinel
- Microsoft Dynamics 365 CRM
- Microsoft OneDrive & Sharepoint
- Microsoft Outlook 365
- Microsoft Power Automate – Preview
- Microsoft Sentiment
- Microsoft Sentinel Threat Intelligence
- Microsoft Teams
- Microsoft Translator
- Microsoft Vision
- Miro
- NetIQ eDirectory
- Nvidia NIM
- Okta
- OpenAI
- OpenAI V1 Compliant LLM
- Oracle Eloqua
- Oracle NetSuite
- PagerDuty
- PayPal
- PDFMonkey
- Perplexity
- Pinecone
- Pipedrive
- QuickBooksOnline
- Quip
- Salesforce
- Salesforce AgentForce & Flows – Preview
- Salesforce Marketing Cloud
- SAP BAPI
- SAP Cloud for Customer
- SAP Concur
- SAP OData
- SendGrid
- ServiceNow
- Shopify
- Slack
- SmartRecruiters
- Smartsheet
- Snowflake
- Snowflake Cortex
- About the Snowflake Cortex connector
- Snowflake Cortex authentication
- Snowflake Cortex features table
- Stripe
- Sugar Enterprise
- Sugar Professional
- Sugar Sell
- Sugar Serve
- System Center - Preview
- TangoCard
- Todoist
- Trello
- Twilio
- UiPath Apps - Preview
- UiPath Data Fabric
- UiPath Test Manager
- UiPath GenAI Activities
- UiPath Orchestrator
- X (formerly Twitter)
- Xero
- watsonx.ai
- WhatsApp Business
- WooCommerce
- Workable
- Workday
- Workday REST
- VMware ESXi vSphere
- YouTube
- Zendesk
- Zoho Campaigns
- Zoho Desk
- Zoho Mail
- Zoom
- ZoomInfo
Connect UiPath to Snowflake Cortex using a Personal Access Token, OAuth 2.0 Authorization code, or OAuth 2.0 Client credentials, by providing your account identifier and related credentials.
Prerequisites
This connector supports three authentication methods: Programmatic Access Token (default), OAuth 2.0 Authorization code, and OAuth 2.0 Client credentials.
To create a connection, you need the following credentials:
- 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:
- 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.
Retrieving your credentials
You can extract the account identifier from your Account Details or from the account server’s URL. For example, in the URL YQXMADF-EWA19151.snowflakecomputing.com the identifier is YQXMADF-EWA19151.
The Personal Access Token (PAT) can be created in the Snowflake dashboard under Settings > Authentication > Programmatic access tokens. You will see the PAT option only if your role allows its creation. Contact your administrator for details.
Using the OAuth 2.0 Authorization code authentication method
By default, users with the ACCOUNTADMIN, ORGADMIN, or SECURITYADMIN role are blocked from using OAuth 2.0 authentication to create a connection. The role you enter in Scope must be granted to the connecting user and must not be one of these three. For details, refer to Snowflake OAuth authorization flow.
To create an OAuth 2.0 client for Snowflake, take the following steps:
-
Run the following query to create the OAuth integration. Make sure to include the correct redirect URL:
https://{baseURL}/provisioning_/callback(for example, for Automation Cloud,https://cloud.uipath.com/provisioning_/callback).CREATE SECURITY INTEGRATION my_oauth_integration_uipath TYPE=OAUTH OAUTH_CLIENT=CUSTOM OAUTH_REDIRECT_URI='https://cloud.uipath.com/provisioning_/callback' OAUTH_CLIENT_TYPE='CONFIDENTIAL' OAUTH_ISSUE_REFRESH_TOKENS=true OAUTH_REFRESH_TOKEN_VALIDITY=86400 ENABLED=true;CREATE SECURITY INTEGRATION my_oauth_integration_uipath TYPE=OAUTH OAUTH_CLIENT=CUSTOM OAUTH_REDIRECT_URI='https://cloud.uipath.com/provisioning_/callback' OAUTH_CLIENT_TYPE='CONFIDENTIAL' OAUTH_ISSUE_REFRESH_TOKENS=true OAUTH_REFRESH_TOKEN_VALIDITY=86400 ENABLED=true; -
Run the following query to view the client details. Copy the
OAUTH_CLIENT_ID.DESCRIBE SECURITY INTEGRATION my_oauth_integration_uipathDESCRIBE SECURITY INTEGRATION my_oauth_integration_uipath -
Run the following query to view the client secret. Copy
OAUTH_CLIENT_SECRET(notOAUTH_CLIENT_SECRET_2).select system$show_oauth_client_secrets('MY_OAUTH_INTEGRATION_UIPATH');select system$show_oauth_client_secrets('MY_OAUTH_INTEGRATION_UIPATH');
For details, refer to Configure Snowflake OAuth for custom clients.
Using the OAuth 2.0 Client credentials authentication method
This method authenticates through Snowflake External OAuth with Microsoft Entra ID instead of Snowflake's own OAuth endpoint: the connector exchanges the Microsoft Entra ID application's client ID and secret for an access token, then sends that token to Snowflake.
To set up OAuth 2.0 Client credentials authentication, configure both Microsoft Entra ID and Snowflake:
- In Microsoft Entra ID, register an application and create a client secret for it. This provides the Client ID and Client Secret, and the Tenant ID is available in the application's Overview section.
- In Microsoft Entra ID, identify (or register) the application representing Snowflake and note its Application ID URI. Use it to build the Scope value:
api://<application-id-uri>/.default. - In Snowflake, create a security integration for external OAuth with the application type set to Azure, the audience set to the Application ID URI from step 2, and a Snowflake user mapped to the service principal's token claim.
For the exact configuration syntax, refer to Snowflake External OAuth with Microsoft Entra ID in the Snowflake documentation.
Add the Snowflake Cortex connection
-
Select Orchestrator from the product launcher.
-
Select a folder, and then navigate to the Connections tab.
-
Select Add connection.
-
To open the connection creation page, select the connector from the list. You can use the search bar to find the connector.
-
Select the authentication type: Programmatic Access Token, OAuth 2.0 Authorization code, or OAuth 2.0 Client credentials.
-
Enter the required credentials and select Connect.
Where available, select the menu next to a field and choose Use credential asset or Use Orchestrator asset to reference an Orchestrator asset instead of entering the value directly. For more information, see Use credential assets for connections.