Actions35
- Genie Actions
- Databricks SQL Actions
- Unity Catalog Actions
- Model Serving Actions
- Files Actions
- Vector Search Actions
Overview
The Databricks node allows users to interact with the Databricks API, specifically targeting various resources such as Databricks SQL, Unity Catalog, Model Serving, Files, Vector Search, and Genie. For the Databricks SQL resource with the List Tables operation, this node fetches a list of tables available in a specified SQL warehouse. This is useful for data engineers or analysts who want to programmatically retrieve metadata about tables within their Databricks environment to automate workflows, generate reports, or integrate with other systems.
Practical examples include:
- Automatically listing all tables in a given SQL warehouse before running queries.
- Building dynamic dashboards that update based on available tables.
- Validating table existence before performing ETL operations.
Properties
| Name | Meaning |
|---|---|
| Warehouse ID | The ID of the SQL warehouse to use. |
| Additional Fields | Optional parameters to refine the query: |
| - Catalog | The catalog to use for the query (optional). |
| - Schema | The schema to use for the query (optional). |
| - Timeout | Query timeout in seconds (default is 60 seconds). |
Output
The node outputs JSON data containing the list of tables retrieved from the specified SQL warehouse. Each item in the output typically represents a table with its associated metadata such as table name, schema, and catalog if provided by the API response.
If the node supports binary data output (not indicated here), it would represent any binary content returned by the API, but for the List Tables operation, the output is purely JSON-based metadata.
Dependencies
- Requires an active Databricks account with access to the SQL warehouses.
- Needs an API authentication token configured in n8n credentials to authorize requests.
- The node uses the base URL and authorization token from the configured credentials to communicate with the Databricks API.
Troubleshooting
Common issues:
- Invalid or missing Warehouse ID will cause the request to fail.
- Incorrect or expired API token will result in authentication errors.
- Specifying a non-existent catalog or schema may return empty results or errors.
- Network connectivity issues can prevent communication with the Databricks API.
Error messages:
- Authentication errors usually indicate invalid or missing API tokens; ensure the credential is correctly set up.
- Timeout errors suggest increasing the "Timeout" property value.
- "Resource not found" or similar errors may mean the Warehouse ID or catalog/schema values are incorrect.