Actions35
- Genie Actions
- Databricks SQL Actions
- Unity Catalog Actions
- Model Serving Actions
- Files Actions
- Vector Search Actions
Overview
The node provides integration with the Genie service within the Databricks platform, specifically enabling users to start a conversation in a designated Genie space. This is useful for automating interactions or initiating dialogues programmatically within a collaborative environment or chatbot framework hosted on Databricks Genie.
Common scenarios include:
- Automatically starting a conversation thread in a specific Genie space as part of a workflow.
- Sending an initial message to trigger downstream processes or notifications.
- Integrating conversational AI or collaboration features into data pipelines or automation tasks.
Example: A user can configure the node to start a conversation in a project-specific Genie space by providing the space ID and an initial message, which could be a status update or a question to team members.
Properties
| Name | Meaning |
|---|---|
| Space ID | The unique identifier of the Genie space where the conversation will be started. |
| Initial Message | The first message content to initiate the conversation in the specified Genie space. |
Output
The node outputs JSON data representing the result of the "start conversation" operation. This typically includes details about the newly created conversation such as its ID, status, timestamps, and possibly metadata about participants or messages.
If binary data were involved (not indicated here), it would represent attachments or media related to the conversation, but this node focuses on JSON structured data only.
Dependencies
- Requires an API authentication token credential configured in n8n to access the Databricks API.
- Needs the base URL of the Databricks instance to send requests.
- The node depends on the Databricks Genie API being accessible and the user having appropriate permissions to create conversations in the specified space.
Troubleshooting
- Invalid Space ID: If the provided space ID does not exist or the user lacks access, the node may return an error indicating the space was not found or permission denied. Verify the space ID and user permissions.
- Authentication Errors: Missing or invalid API tokens will cause authorization failures. Ensure the API key or token credential is correctly set up.
- Empty Initial Message: Since the initial message is required, leaving it empty will likely cause validation errors before execution.
- API Rate Limits or Network Issues: Temporary failures might occur due to rate limiting or connectivity problems; retrying after some time or checking network settings can help.
Links and References
- Databricks Genie API Documentation (example link, replace with actual if available)
- n8n Documentation on Creating Custom Nodes
- Databricks Official Site