Actions42
- Genie Actions
- Databricks SQL Actions
- Unity Catalog Actions
- Model Serving Actions
- Files Actions
- Vector Search Actions
Overview
This node interacts with the Genie API of the Databricks platform, specifically to manage conversation messages within Genie spaces. The "Get Conversation Message" operation retrieves a specific message from a conversation in a designated Genie space.
Typical use cases include:
- Fetching details or content of a particular message in a conversation for auditing or processing.
- Integrating Genie conversations into workflows where message data needs to be analyzed or forwarded.
- Automating responses or follow-up actions based on retrieved message content.
For example, you might use this node to get a message by its ID from a conversation and then trigger further processing such as sentiment analysis or logging.
Properties
| Name | Meaning |
|---|---|
| Space ID | The unique identifier of the Genie space containing the conversation. |
| Conversation ID | The unique identifier of the conversation within the specified Genie space. |
| Message ID | The unique identifier of the message to retrieve from the specified conversation. |
Output
The output is a JSON object representing the retrieved message from the Genie API. It contains all the details of the message as returned by the API, which typically includes message content, metadata, timestamps, sender information, and any other relevant fields defined by the Genie service.
No binary data output is produced by this operation.
Example output structure (simplified):
{
"id": "messageId",
"content": "Message text or payload",
"createdAt": "timestamp",
"sender": {
"id": "userId",
"name": "User Name"
},
...
}
Dependencies
- Requires an API authentication token credential for Databricks with access to the Genie API.
- The node uses the base URL and token from the configured credentials to make HTTP requests.
- No additional external dependencies are required beyond the Databricks Genie API.
Troubleshooting
Common issues:
- Invalid or missing Space ID, Conversation ID, or Message ID will cause the API request to fail.
- Authentication errors if the API token is invalid or lacks necessary permissions.
- Network connectivity problems preventing communication with the Databricks API endpoint.
Error messages:
API Error: <status code> <status text>: Indicates the Genie API responded with an error status. Check that IDs are correct and the token has proper access.Network Error: No response received from server: Suggests network issues or incorrect base URL configuration.- Other unexpected errors will be logged with their message and stack trace if continue-on-fail is enabled.
Resolution tips:
- Verify all input IDs are accurate and correspond to existing resources.
- Ensure the API token credential is valid and has appropriate scopes.
- Confirm network connectivity and that the Databricks host URL is correctly set in credentials.
Links and References
- Databricks Genie API Documentation (hypothetical link; replace with actual)
- n8n HTTP Request Node Documentation (for understanding underlying HTTP calls)
- Databricks Platform Overview