Overview
The Symbiosika Chat History node retrieves the chat history for a specified chat from the Symbiosika platform. It is useful when you want to fetch past conversation data for analysis, auditing, or integration with other workflows. For example, you might use this node to pull chat histories for customer support conversations to feed into a reporting system or to trigger follow-up actions based on previous interactions.
Properties
| Name | Meaning |
|---|---|
| Organisation Name or ID | Select the organisation from which to retrieve chat history. You can choose from a list or specify an ID. |
| Chat ID Source | Choose where to get the chat ID from: either from an input field in the incoming data or manual entry. |
| Chat ID | (Shown if "Manual Entry" selected) The specific chat ID to retrieve history for. |
| Chat ID Field | (Shown if "Input Field" selected) The name of the field in the input data that contains the chat ID. |
Output
The node outputs an array of items, each containing the original input data merged with a new field:
chatHistoryResponse: This JSON object contains the full chat history retrieved from the Symbiosika API for the specified chat ID.
If an error occurs and the node is set to continue on failure, the output item will include an error field describing the issue instead of the chat history.
Dependencies
- Requires an API key credential for authenticating with the Symbiosika API.
- The node makes HTTP GET requests to the Symbiosika API endpoint to fetch organisations and chat histories.
- The API base URL and key must be configured in the credential used by the node.
Troubleshooting
- No chat ID provided: This error occurs if the chat ID is missing from the specified input field or manual entry. Ensure the chat ID is correctly supplied.
- Invalid response format for organisations: Indicates the API did not return the expected list of organisations. Check API availability and credentials.
- Failed to load organisations: Could be due to network issues or invalid API key. Verify credentials and connectivity.
- Invalid response from Symbiosika API for chat ID: The chat history request returned unexpected data or no data. Confirm the chat ID exists and belongs to the selected organisation.
- To handle errors gracefully, enable "Continue On Fail" so the workflow can proceed even if some items fail.
Links and References
- n8n Expressions Documentation
- Symbiosika API documentation (not included in source; consult your Symbiosika API docs for details)