Actions35
- Genie Actions
- Databricks SQL Actions
- Unity Catalog Actions
- Model Serving Actions
- Files Actions
- Vector Search Actions
Overview
This node integrates with the Databricks API, specifically supporting multiple resources including "Genie." For the Genie resource, it allows operations such as retrieving a specific conversation message by its ID. This is useful in scenarios where you want to fetch details of a particular message from a conversation managed or stored within Databricks Genie service.
Practical examples include:
- Fetching the content and metadata of a specific message in a chatbot conversation for analysis or display.
- Retrieving historical messages to audit or review interactions.
- Integrating message retrieval into workflows that automate customer support or conversational AI processes.
Properties
| Name | Meaning |
|---|---|
| Message ID | The ID of the message to retrieve. This is a required string input specifying which conversation message to get from the Genie resource. |
Output
The node outputs JSON data representing the retrieved conversation message. This typically includes the message content, metadata such as timestamps, sender information, and any other relevant fields returned by the Databricks Genie API for a message.
If the node supports binary data output (not indicated here), it would represent attachments or media related to the message, but based on the provided code and properties, the output is JSON only.
Dependencies
- Requires an active Databricks API connection configured with:
- A valid host URL.
- An API authentication token (provided via credentials).
- The node depends on the Databricks Genie API endpoint to fetch conversation messages.
Troubleshooting
- Missing or invalid Message ID: Since the Message ID is required, ensure it is provided and correctly formatted. Errors will occur if this is empty or incorrect.
- Authentication errors: If the API token or host is misconfigured, the node will fail to connect. Verify credentials are correct and have necessary permissions.
- Message not found: If the specified Message ID does not exist, the API may return a not found error. Confirm the ID is valid and corresponds to an existing message.
- Network issues: Connectivity problems can cause request failures. Check network access to the Databricks instance.
Links and References
- Databricks API Documentation — for detailed API endpoints and parameters.
- n8n Documentation — for general guidance on using and configuring nodes and credentials.