Actions35
- Genie Actions
- Databricks SQL Actions
- Unity Catalog Actions
- Model Serving Actions
- Files Actions
- Vector Search Actions
Overview
The node provides integration with Databricks, allowing users to interact with various Databricks services through a unified interface. Specifically, for the Files resource and the Get File operation, the node retrieves a file from a specified path within the Databricks workspace.
This operation is useful when you need to programmatically access files stored in Databricks, such as configuration files, logs, or data files, directly within an n8n workflow. For example, you might use this node to fetch a notebook or dataset file before processing it further or transferring it to another system.
Properties
| Name | Meaning |
|---|---|
| Path | The full path to the file in the Databricks workspace that you want to retrieve. Example: /Volumes/my-catalog/my-schema/my-volume/directory/file.txt. This path must be accurate to locate the desired file. |
Output
The output of the node includes a json field containing the file's metadata and content information retrieved from Databricks. If the file contains binary data, the node may also provide this data in a binary format suitable for further processing or saving.
json: Contains details about the file fetched, such as its path, size, modification date, and possibly the file content encoded appropriately.binary: If applicable, holds the raw binary data of the file, enabling workflows to handle files like images, documents, or other non-text formats.
Dependencies
- Requires an API authentication token credential to connect securely to the Databricks workspace.
- The node depends on the Databricks REST API endpoint configured via the host URL.
- Proper permissions on the Databricks workspace are necessary to read files at the specified paths.
Troubleshooting
- File Not Found: If the specified path is incorrect or the file does not exist, the node will likely return an error indicating the file could not be found. Verify the exact path and ensure the file exists in the Databricks workspace.
- Authentication Errors: Missing or invalid API tokens will cause authorization failures. Ensure the API key/token credential is correctly set up and has sufficient privileges.
- Permission Denied: Even with valid credentials, insufficient permissions on the file or directory can cause access errors. Confirm that the user associated with the token has read access to the target file.
- Invalid Path Format: Paths must follow the expected format for Databricks workspace files. Incorrect formatting may lead to errors or unexpected results.