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 platform, allowing users to interact with various Databricks services through a unified interface. Specifically, for the "Genie" resource and the "Get Genie Space" operation, the node retrieves information about a specific Genie space by its ID. This is useful in scenarios where you want to programmatically access metadata or details about a Genie space within Databricks, such as for monitoring, automation, or reporting purposes.
Practical examples include:
- Fetching details of a Genie space before starting a conversation or performing other operations.
- Automating workflows that depend on the state or configuration of a Genie space.
- Integrating Genie space data into dashboards or external systems.
Properties
| Name | Meaning |
|---|---|
| Space ID | The ID of the Genie space to retrieve information about. This is a required string input. |
Output
The output contains a JSON object representing the details of the requested Genie space. This typically includes metadata and configuration information related to that space. The exact structure depends on the Databricks Genie API response but generally includes identifiers, names, descriptions, and possibly status or settings of the space.
If the node supports binary data output (not indicated here), it would represent any associated files or attachments related to the Genie space, but this is not evident from the provided code.
Dependencies
- Requires an active connection to Databricks via an API token or similar authentication method.
- The node expects credentials configured in n8n that provide access to the Databricks API endpoint.
- Network access to the Databricks instance specified in the credentials is necessary.
Troubleshooting
- Invalid or missing Space ID: Ensure the Space ID property is correctly set and corresponds to an existing Genie space.
- Authentication errors: Verify that the API token or credentials used have sufficient permissions to access Genie spaces.
- Network issues: Confirm that the Databricks host URL is reachable from the n8n environment.
- API changes or deprecations: If the Genie API changes, the node might fail; check for updates or patches.
- Error messages typically include HTTP status codes like 401 (Unauthorized), 404 (Not Found if the space ID does not exist), or 500 (Server error). Resolving these involves checking credentials, verifying the space ID, and ensuring the Databricks service is operational.
Links and References
- Databricks Genie API Documentation (example link, replace with actual)
- n8n Documentation on Credentials
- Databricks Official Site