Actions42
- Genie Actions
- Databricks SQL Actions
- Unity Catalog Actions
- Model Serving Actions
- Files Actions
- Vector Search Actions
Overview
This node integrates with the Genie API of the Databricks platform to manage conversations within Genie spaces. Specifically, the "Create Conversation Message" operation allows users to send a new message into an existing conversation inside a specified Genie space.
Typical use cases include automating interactions in collaborative environments where Genie is used for conversational AI or team communication. For example, you might use this node to programmatically add messages to ongoing discussions, trigger workflows based on conversation content, or integrate Genie conversations with other systems.
Properties
| Name | Meaning |
|---|---|
| Space ID | The unique identifier of the Genie space where the conversation exists. |
| Conversation ID | The unique identifier of the conversation within the specified Genie space. |
| Message | The text content of the message to be sent into the conversation in the Genie space. |
Output
The node outputs a JSON object representing the response from the Genie API after creating the message. This typically includes details about the newly created message such as its ID, content, timestamps, and any metadata returned by the API.
No binary data output is produced by this operation.
Dependencies
- Requires an API authentication token credential configured in n8n to authorize requests to the Databricks Genie API.
- The node makes HTTP requests to the Databricks Genie REST endpoints, so network connectivity to the Databricks environment is necessary.
- Proper permissions on the Genie space and conversation are required for message creation.
Troubleshooting
- API Errors: If the API returns errors (e.g., 4xx or 5xx status codes), the node will log the status and error details. Common causes include invalid Space ID or Conversation ID, insufficient permissions, or malformed message content. Verify that all IDs are correct and that the API token has appropriate access rights.
- Network Issues: If no response is received from the server, it may indicate network connectivity problems or incorrect host configuration. Ensure the Databricks host URL is reachable and correctly set in credentials.
- Invalid Parameters: Missing or empty required parameters like Space ID, Conversation ID, or Message will cause the request to fail. Double-check that these inputs are provided and valid.
- Continue On Fail: If enabled, the node will continue processing subsequent items even if some fail, returning error details in the output JSON. Otherwise, execution stops at the first error.
Links and References
- Databricks Genie API Documentation (for detailed API endpoint info)
- n8n HTTP Request Node Documentation (for understanding HTTP request handling in n8n)