Actions35
- Genie Actions
- Databricks SQL Actions
- Unity Catalog Actions
- Model Serving Actions
- Files Actions
- Vector Search Actions
Overview
The node provides integration with the Databricks API, specifically allowing interaction with various Databricks resources including Unity Catalog. For the Unity Catalog resource, the "Get Table" operation retrieves metadata or details about a specific table within a given catalog and schema.
This node is useful in scenarios where users want to programmatically access metadata about tables stored in Databricks Unity Catalog, for example:
- Automating data cataloging workflows.
- Validating table existence or structure before running queries.
- Integrating Databricks metadata into other systems or dashboards.
Properties
| Name | Meaning |
|---|---|
| Catalog | The catalog name within Unity Catalog where the target table resides. |
| Schema | The schema name inside the specified catalog to scope the table query. |
These properties are required inputs to specify the exact location of the table in the Unity Catalog hierarchy.
Output
The output JSON will contain the details of the requested table from Unity Catalog. This typically includes metadata such as table name, columns, types, creation time, and other relevant attributes describing the table structure and properties.
If the node supports binary data output (not evident from the provided code), it would represent any associated binary content related to the table, but this is unlikely for a metadata retrieval operation.
Dependencies
- Requires an active Databricks API connection configured with:
- A valid host URL for the Databricks workspace.
- An API authentication token (API key) with permissions to access Unity Catalog metadata.
- No additional external dependencies beyond the n8n environment and the Databricks API.
Troubleshooting
Common issues:
- Invalid or missing API token leading to authentication errors.
- Incorrect catalog or schema names causing "table not found" or similar errors.
- Insufficient permissions on the Databricks side to access Unity Catalog metadata.
Error messages:
- Authentication failures: Check that the API token is correct and has necessary scopes.
- Resource not found: Verify that the catalog and schema names are spelled correctly and exist.
- Network or connectivity errors: Ensure the host URL is reachable from the n8n instance.
Resolving these usually involves verifying credentials, input parameters, and network accessibility.