Overview
This node retrieves the current state of a specific thread from an external service. It is useful in scenarios where you need to monitor or track the status of threads managed by an API, such as customer support conversations, background jobs, or process threads. For example, you might use this node to check if a support ticket thread is open, closed, or pending, enabling automated workflows based on thread status.
Properties
| Name | Meaning |
|---|---|
| Thread ID | The unique identifier of the thread whose state you want to retrieve. |
Output
The node outputs a JSON array where each element corresponds to the state information of a requested thread. Each item contains the data returned by the external API endpoint for that thread's state. This typically includes details about the thread's current status.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential to authenticate with the external service.
- The node makes HTTP GET requests to the endpoint
/agent/threads/{threadId}/stateon the configured API base URL. - The API base URL and authentication token must be configured in the node’s credentials.
Troubleshooting
- Missing or invalid Thread ID: Ensure the "Thread ID" property is provided and correctly formatted; otherwise, the API call will fail.
- Authentication errors: Verify that the API key credential is valid and has sufficient permissions to access thread state information.
- Network or API errors: Check network connectivity and confirm the external service is reachable at the configured URL.
- Unexpected response format: If the API changes its response structure, the node may not handle it correctly; verify the API documentation for updates.
Links and References
- Refer to the external service’s API documentation for details on the
/agent/threads/{threadId}/stateendpoint and possible thread states.