Databricks package - Databricks connector enables seamless integration with your automation workflows, allowing you to run SQL queries, manage jobs, and handle files directly within Databricks .

Automation 360

Databricks connector enables seamless integration with your automation workflows, allowing you to run SQL queries, manage jobs, and handle files directly within Databricks.

You can now connect to Databricks directly from your automation workflows, making it easier to work with your data, run queries, and manage data processing tasks—all in one place. With this connector, you can
  • Run SQL queries on your Databricks data and process large datasets with ease.
  • Retrieve query results efficiently, even for high-volume data, using a scalable approach.
  • Stop long-running queries when needed to maintain control over execution.
  • View and manage jobs in your Databricks workspace, including running jobs and checking their status.
  • Run existing jobs and monitor their progress and outcomes.
  • Access job results and outputs for better visibility into your workflows.
  • Upload files to Databricks for processing.
  • Download files from Databricks to your local environment.
  • Delete files when no longer needed.
Note:
  • The Databricks package supports integration withDatabricks application deployed on Amazon Web Services (AWS), Microsoft Azure, and Google Cloud Platform (GCP).
  • The Databricks package includes an user-agent header in requests sent to Databricks. The header uses the AutomationAnywhere_Automation360 format.

    Databricks can use this information to identify requests originating from Automation Anywhere and for usage telemetry.

Prerequisites

  • Ensure that you configured OAuth connection in your Databricks account. For more details, see Configure OAuth connection in Databricks platform.
  • The below table summarizes the key Unity Catalog (UC) and Databricks platform objects that must be provisioned and accessible to support each category of Automation Anywhere Databricks package actions. These objects form the foundational prerequisites for authentication, data access, file operations, and job execution within a governed Databricks environment. Also, it lists the recommended Unity Catalog setup for the entire Databricks package.
    Action group Unity Catalog (UC) objects
    Authentication
    • Databricks Service Principal (preferred)
    • OAuth Machine-to-Machine (M2M) authentication
    • Workspace assignment for the service principal
    Data governance
    • UC enabled workspace
    • At least one Catalog and Schema
    • Privilege grants:
      • USE CATALOG
      • USE SCHEMA
      • SELECT
      • MODIFY (if applicable)
    SQL actions
    File actions
    • Unity Catalog Volumes OR External locations
    • Volume or External location, Storage credential
    • Storage Credentials configured

    • Grants:

      • READ FILES
      • WRITE FILES
      For more details, see Delete file action prerequisites.
    Job actions
    • Jobs configured to run with User identity or Service principal identity
    • Access to all UC-governed assets used by workflows and SQL queries
    • Job, Compute, Catalogs/Schemas/Tables used by job
    • Job-level CAN RUN or equivalent permission
    Connection actions Service principal, OAuth app, UC-enabled workspace

For more details about Unity Catalog, see Databricks Unity Catalog.

Actions in the Databricks package

Action Description
Cancel job run Cancel job run action
Cancel SQL statement Cancel SQL statement action
Connect Connect action for Databricks
Delete file Delete file action
Disconnect Disconnect action in the Databricks package
Download file Download file action
Execute SQL statement Execute SQL statement action
Get job run output Get job run output action
Get job run status Get job run status action
Get SQL statement result Get SQL statement result action
List jobs List jobs action
Run job Run job action
Upload file Upload file action