Lis - Get Thread History

Overview

This node retrieves the execution history of a specific thread from an external service. It is useful when you want to track or audit the sequence of events or actions that have occurred within a particular thread, such as in customer support conversations, task processing threads, or workflow executions. For example, you might use this node to fetch all past messages or status changes related to a support ticket thread to analyze its progression.

Properties

Output

The node outputs a JSON array where each element represents the execution history data retrieved for the specified thread. This typically includes details about the thread's past events or actions as returned by the external service's API. There is no binary output.

Dependencies

• Requires an API key credential to authenticate with the external service.
• The node makes HTTP GET requests to the endpoint /agent/threads/{threadId}/history on the configured service URL.
• The user must configure the API base URL and provide valid credentials for the external service.

Troubleshooting

• Invalid or missing Thread ID: If the Thread ID is not provided or incorrect, the API request will fail. Ensure the Thread ID is correctly set and corresponds to an existing thread.
• Authentication errors: If the API key or credentials are invalid or missing, the node will fail to authenticate. Verify that the API credentials are correctly configured.
• Network or service errors: If the external service is unreachable or returns an error, the node will throw an error. Check network connectivity and service status.
• Unexpected response format: If the external API changes its response structure, the node may not handle it properly. Review API documentation and update the node if necessary.

Links and References

• Refer to the external service's API documentation for details on the /agent/threads/{threadId}/history endpoint.
• n8n HTTP Request node documentation for understanding how HTTP requests are made within nodes.