Actions35
- Genie Actions
- Databricks SQL Actions
- Unity Catalog Actions
- Model Serving Actions
- Files Actions
- Vector Search Actions
Overview
The node enables interaction with the Databricks API, specifically supporting multiple resources including "Genie". For the "Genie" resource, it allows creating conversation messages by sending a message to a specified conversation ID. This is useful in scenarios where automated or programmatic messaging within Databricks Genie conversations is needed, such as triggering alerts, adding context, or integrating chat-based workflows.
Example use cases:
- Automatically posting status updates or results into a Databricks Genie conversation.
- Integrating external systems to send messages into Databricks chat threads.
- Logging or annotating conversations programmatically during data workflows.
Properties
| Name | Meaning |
|---|---|
| Conversation ID | The ID of the conversation to post the message to. |
| Message | The content of the message to be sent. |
Output
The node outputs JSON data representing the response from the Databricks API after creating the conversation message. This typically includes details about the created message such as its ID, timestamp, and content confirmation. There is no indication that binary data is output by this operation.
Dependencies
- Requires an active Databricks API connection configured with:
- A base URL (Databricks host).
- An API authentication token (Bearer token).
- The node depends on the n8n workflow environment and the bundled Databricks API client code.
Troubleshooting
- Missing or invalid credentials: Ensure the Databricks API token and host are correctly set up in n8n credentials.
- Invalid Conversation ID: If the conversation ID does not exist or is incorrect, the API will likely return an error. Verify the conversation ID before running.
- Empty message content: The message property is required; sending an empty string may cause errors.
- API rate limits or permissions: Insufficient permissions or hitting API rate limits can cause failures. Check Databricks user roles and API usage quotas.
Links and References
- Databricks API Documentation (general reference for API endpoints)
- n8n Documentation for configuring credentials and using custom nodes