Actions42
- Genie Actions
- Databricks SQL Actions
- Unity Catalog Actions
- Model Serving Actions
- Files Actions
- Vector Search Actions
Overview
This node integrates with the Databricks platform, specifically supporting operations on various Databricks resources including Unity Catalog. The "Get Function" operation under the Unity Catalog resource allows users to retrieve metadata or details about a specific function defined within a Unity Catalog schema.
Typical use cases include:
- Automating retrieval of function definitions or metadata from Unity Catalog for auditing or documentation.
- Integrating Databricks Unity Catalog functions into data workflows by fetching their details dynamically.
- Building dashboards or reports that require up-to-date information about cataloged functions in Databricks.
For example, a user might select a catalog and schema, then fetch details about a particular function to verify its parameters or usage before invoking it elsewhere.
Properties
| Name | Meaning |
|---|---|
| Catalog | Selects the Unity Catalog to work with. The list is dynamically loaded from your Databricks workspace catalogs. |
| Schema | Selects a schema within the chosen catalog. The list is dynamically populated based on the selected catalog. |
Note: The provided properties snippet only includes Catalog and Schema. The actual "Get Function" operation likely requires additional parameters (e.g., function name), but these are not included in the provided input.
Output
The node outputs JSON data representing the response from the Databricks Unity Catalog API for the requested function. This typically includes detailed metadata about the function such as its name, parameters, return type, and possibly comments or descriptions.
If the node supports binary data output (not indicated here), it would be summarized accordingly, but this operation primarily deals with JSON metadata.
Dependencies
- Requires an active Databricks API authentication token configured in n8n credentials.
- Access to the Databricks workspace where the Unity Catalog resides.
- Network connectivity to the Databricks API endpoint specified in the credentials.
Troubleshooting
Common Issues:
- Incorrect or expired API token leading to authentication failures.
- Selecting a catalog or schema that does not exist or to which the user lacks access.
- Network issues preventing communication with the Databricks API.
Error Messages:
API Error: <status> <statusText>: Indicates the API returned an error status. Check the status code and message for details (e.g., 401 Unauthorized means invalid credentials).Network Error: No response received from server: Suggests network connectivity problems or incorrect API host configuration.- Other errors will include stack traces if continue-on-fail is enabled; otherwise, they will halt execution.
Resolutions:
- Verify and refresh API credentials.
- Confirm catalog and schema names are correct and accessible.
- Ensure the Databricks host URL is correctly set in credentials.
- Check network/firewall settings to allow outbound requests to Databricks.