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 supporting multiple resources including "Genie". For the "Genie" resource and the "Get Query Results" operation, the node retrieves the results of a previously executed query message. This is useful in scenarios where you have submitted a query to Databricks Genie and want to fetch the output data once the query execution is complete.
Practical examples include:
- Fetching the results of a SQL query run asynchronously on Databricks Genie.
- Retrieving data from a specific message attachment related to a query result for further processing or analysis within an n8n workflow.
Properties
| Name | Meaning |
|---|---|
| Message ID | The unique identifier of the message whose query results you want to retrieve. |
| Attachment ID | The unique identifier of the attachment within the message that contains the query data. |
Output
The node outputs the JSON data representing the query results fetched from the specified message attachment. The structure typically includes rows of data returned by the query. If the query results include binary attachments (e.g., files), those would be accessible as binary data attached to the output item.
Dependencies
- Requires an active connection to the Databricks API using an API authentication token.
- The node expects credentials containing the Databricks host URL and a valid bearer token for authorization.
- No additional external dependencies beyond the Databricks API are required.
Troubleshooting
- Invalid Message ID or Attachment ID: If the provided IDs do not exist or are incorrect, the node will fail to retrieve results. Verify the IDs correspond to existing messages and attachments.
- Authorization Errors: Ensure the API token has sufficient permissions to access Genie query results.
- Network Issues: Connectivity problems to the Databricks API endpoint can cause failures; check network settings and API availability.
- Empty Results: If the query has not completed or returned no data, the output may be empty. Confirm the query execution status before fetching results.
Links and References
- Databricks Genie API Documentation (for detailed API endpoints and parameters)
- n8n Documentation on HTTP Request Nodes (general guidance on API integrations)