- Erste Schritte
- Benachrichtigungen
- Lizenzierung
- Fehlersuche und ‑behebung
- Codierungs-Agents
- Connector Builder
- Über Connector Builder
- Erstellen Ihres ersten Connectors
- Erstellen Ihres Connectors aus einer API-Definition
- Konfigurieren der Authentifizierung
- Verwenden von Variablen im Connector-Generator
- Aktivitätsdesigner
- Erstellen eines Triggers
- Skript
- Checkliste für den Connector Builder
- Erste Schritte
- Beispiel A: Erstellen Sie einen Connector aus einer leeren Canvas mit Authentifizierung mit persönlichem Zugriffstoken
- Beispiel B: Erstellen Sie einen Connector aus einer leeren Canvas mit API-Schlüsselauthentifizierung
- Beispiel C: Erstellen eines Connectors aus einer API-Spezifikation mit OAuth 2.0 Client-Anmeldeinformationenauthentifizierung
- Act! 365
- ActiveCampaign
- Active Directory – Vorschau
- Adobe Acrobat Sign
- Adobe PDF Services
- Agent 2 Agent – Vorschau
- 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
- Team AI – Vorschau
- Customer.io
- Database Hub
- Databricks - Preview
- About the Databricks connector
- Databricks authentication
- Databricks-Agent
- Datadog
- DeepSeek
- Deputy
- Discord – Vorschau
- DocuSign
- Drop
- Dropbox
- Dropbox Business
- Egnyte
- Epic FHIR – Vorschau
- Eventbrite
- Wechselkurse
- Exchange Server – Vorschau
- Expensify
- Facebook
- Freshbooks
- Freshdesk
- Freshsales
- Freshservice
- GetResponse
- GitHub
- Gmail
- Google Cloud Platform
- Google Docs
- Google Drive
- Google Formulare – Vorschau
- Google Maps
- Google Tabellen
- Google Sprache-zu-Text
- Google Text-to-Speech
- Google Tasks – Vorschau
- Google Vertex
- Google Vision
- Google Workspace
- GoToWebinar
- Greenhouse
- Hootsuite
- http
- HTTP-Webhook
- Hubspot CRM
- HubSpot Marketing
- HyperV – Vorschau
- Icertis
- iContact
- Insightly CRM
- Intercom
- Jina.ai
- Jira
- Keap
- Klaviyo
- LinkedIn
- E-Mail (Mail)
- Mailchimp
- Mailgun
- Mailjet
- MailerLite
- Marketo
- MCP
- Microsoft 365
- Microsoft Azure
- Microsoft Azure Active Directory
- Microsoft Azure AI Foundry
- Microsoft Azure OpenAI
- Microsoft Azure Sentinel
- Microsoft Dynamics 365 CRM
- Microsoft OneDrive und SharePoint
- Microsoft Outlook 365
- Microsoft Power Automate
- Microsoft Sentiment
- Microsoft Sentinel-Threat Intelligence
- Microsoft Teams
- Microsoft Translator
- Microsoft Vision
- Miro
- NetIQ eDirectory
- NVIDIA NIM
- Okta
- OpenAI
- OpenAI V1-konformes LLM
- Oracle Eloqua
- Oracle NetSuite
- PagerDuty
- Paypal
- PDFMonkey
- Perplexity
- Pinecone
- Pipedrive
- QuickBooksOnline
- Quip
- Salesforce
- Salesforce Agentforce & Flows
- Salesforce Marketing Cloud
- SAP BAPI
- SAP Cloud for Customer
- SAP Concur
- SAP OData
- SendGrid
- ServiceNow
- Shopify
- Slack
- SmartRecruiters
- Smartsheet
- Snowflake
- Snowflake Cortex
- Stripe
- Sugar Enterprise
- Sugar Professional
- Sugar Sell
- Sugar Serve
- System Center – Vorschau
- TangoCard
- Todoist
- Trello
- Twilio
- TypeSafe – Vorschau
- UiPath Apps - Preview
- UiPath Data Fabric
- UiPath Test Manager
- UiPath GenAI-Aktivitäten
- UiPath Orchestrator
- X (früher Twitter)
- Xero
- wassonx.ai zu senden
- WhatsApp Business
- WooCommerce
- Durchführbar
- Workday
- Workday REST
- VMware ESXi vSphere
- YouTube
- Zendesk
- Zoho Campaigns
- Zoho-Desktop
- Zoho Mail
- Zoom
- ZoomInfo
Databricks authentication
Connect UiPath to a Databricks workspace using OAuth 2.0 client credentials with a Databricks OAuth service principal or a Microsoft Entra ID service principal.
Voraussetzungen
The Databricks connector authenticates as a service principal using OAuth 2.0 client credentials (machine-to-machine). Two kinds of service principal are supported:
- A Databricks OAuth service principal, managed in the Databricks account console.
- A Microsoft Entra ID service principal, for Azure Databricks workspaces.
To create a connection, you need the following values:
| Feld | Beschreibung |
|---|---|
| Workspace Host | Workspace hostname only, without https:// or a trailing slash. For example, adb-1234567890123456.7.azuredatabricks.net. |
| Client-ID | The service principal's Application ID (UUID). |
| Geheimer Clientschlüssel | An OAuth secret generated for that service principal. This is not a personal access token. |
| OAuth Token URL | The token endpoint. Defaults to https://{workspace.host}/oidc/v1/token. |
| OAuth-Geltungsbereich | The requested scope. Defaults to all-apis. |
Abrufen Ihrer Anmeldeinformationen
-
Extract the Workspace Host from your Databricks workspace URL. For example, in
https://adb-1234567890123456.7.azuredatabricks.net/browse/folders/workspace, the workspace host isadb-1234567890123456.7.azuredatabricks.net. -
In the Databricks account console, go to User management > Service principals and create a service principal, or select an existing one.
-
Copy the service principal's Application ID (UUID) — this is the Client ID.
-
On the service principal, go to Secrets > Generate secret and copy the generated OAuth secret — this is the Client Secret. The secret is shown only once.
Wichtig:Use an OAuth secret, not a personal access token. Personal access tokens are not supported by this connector.
-
Grant the service principal access to the workspace and to every object your automation uses, such as the SQL warehouse, jobs, Unity Catalog securables, volumes, Genie spaces, and Vector Search indexes.
For more information, see OAuth machine-to-machine (M2M) authentication and Manage service principals in the Databricks documentation.
The default OAuth Scope of all-apis lets the token reach every API the service principal is authorized for. Databricks also supports scoped OAuth secrets, which restrict a secret to a specific set of API scopes such as sql, jobs, or unity-catalog. If you use one, the scope must still cover every Databricks API your automation calls, or those activities fail at runtime.
Add the Databricks connection
-
Wählen Sie Orchestrator im Produktstartprogramm aus.
-
Wählen Sie einen Ordner aus und navigieren Sie dann zur Registerkarte Verbindungen .
-
Wählen Sie Verbindung hinzufügen aus.
-
Um die Seite zur Erstellung der Verbindung zu öffnen, wählen Sie den Konnektor in der Liste aus. Sie können die Suchleiste verwenden, um den Connector zu finden.
-
Enter the Workspace Host, Client ID, and Client Secret.
Wenn verfügbar, wählen Sie das Menü neben einem Feld und dann Anmeldeinformations-Asset verwenden oder Orchestrator-Asset verwenden aus , um auf ein Orchestrator-Asset zu verweisen, anstatt den Wert direkt einzugeben. Weitere Informationen finden Sie unter Verwenden von Anmeldeinformationsassets für Verbindungen.
If you are using a Microsoft Entra ID service principal, update OAuth Token URL and OAuth Scope as described in Use a Microsoft Entra ID service principal. Otherwise, leave both fields at their defaults.
-
Select Connect.
Your Databricks connection has now been added and is available for use in UiPath Studio or Studio Web.
Use a Microsoft Entra ID service principal
If you authenticate with a Microsoft Entra ID service principal instead of a Databricks OAuth service principal, change OAuth Token URL and OAuth Scope as follows:
-
Replace the OAuth Token URL entirely with the Microsoft identity platform token endpoint:
https://login.microsoftonline.com/{your-azure-tenant-guid}/oauth2/v2.0/tokenhttps://login.microsoftonline.com/{your-azure-tenant-guid}/oauth2/v2.0/tokenWichtig:Substitute your literal Azure tenant GUID into the URL. Do not leave
{your-azure-tenant-guid}as a placeholder. -
Set OAuth Scope to the Azure Databricks resource ID followed by
/.default:2ff814a6-3304-4ab8-85cb-cd0e6f879c1d/.default2ff814a6-3304-4ab8-85cb-cd0e6f879c1d/.defaultHinweis:Unlike the tenant GUID in the token URL, this GUID is not a placeholder.
2ff814a6-3304-4ab8-85cb-cd0e6f879c1dis the fixed identifier for Azure Databricks across all Azure environments, so enter it exactly as shown.
For more information, see Get Microsoft Entra ID tokens manually and Authenticate with Microsoft Entra service principals in the Azure Databricks documentation.
The connection is only as capable as the service principal behind it. A connection can be created successfully and still fail at runtime if the service principal lacks permissions on the object an activity targets.