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 associated with a particular chat ID within an organization. This can help in scenarios such as analyzing previous interactions, auditing conversations, or integrating chat histories into workflows for further processing.
For example, you might use this node to:
- Automatically pull chat histories for customer support chats to analyze common issues.
- Aggregate chat logs for compliance or record-keeping purposes.
- Feed historical chat data into AI models or reporting tools.
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: either from an input field in the incoming data or by manual entry. |
| Chat ID | (Shown if "Manual Entry" selected) Manually enter the chat ID to retrieve history for. |
| Chat ID Field | (Shown if "Input Field" selected) Specify the name of the field in the input data that contains the chat ID. |
Output
The node outputs an array of items corresponding to each input item processed. Each output item contains:
json.chatHistoryResponse: The full response object returned by the Symbiosika API containing the chat history for the specified chat ID.- All original input JSON fields are preserved and merged with the new
chatHistoryResponsefield.
If the node encounters an error and "Continue On Fail" is enabled, the output item will contain an error field describing the issue instead of the chat history.
Dependencies
- Requires an API key credential for authenticating with the Symbiosika API.
- Needs network access to the Symbiosika API endpoint specified in the credential.
- The node dynamically loads available organisations via the API to populate the organisation selection dropdown.
Troubleshooting
- No chat ID provided: If the chat ID is missing from the specified input field or manual entry, the node will throw an error indicating no chat ID was provided for that item.
- Invalid response from API: If the API returns an unexpected or empty response, the node will raise an error specifying the chat ID involved.
- Failed to load organisations: When loading organisation options, network issues or invalid credentials may cause failure. Ensure the API key is valid and the endpoint is reachable.
- To handle errors gracefully, enable "Continue On Fail" so that processing continues even if some items fail.
Links and References
- n8n Expressions Documentation
- Symbiosika API documentation (not publicly linked here; refer to your internal resources)