Actions22
- Chat Actions
- Channel Actions
- Message Actions
- Contact Actions
- OTP Code Actions
- OTP Link Actions
Overview
This node interacts with the CrunchzApp API to unarchive a chat associated with a specific contact. It is useful in scenarios where archived chats need to be restored to active status for further communication or processing. For example, if a user previously archived a conversation with a customer and now wants to resume messaging, this node can unarchive that chat by specifying the contact's ID.
Properties
| Name | Meaning |
|---|---|
| Contact Id | The unique identifier of the contact whose chat you want to unarchive. Format: xxx@c.us |
Output
The node outputs JSON data representing the response from the CrunchzApp API after attempting to unarchive the specified chat. This typically includes confirmation of success or details about the updated chat status. There is no indication that binary data is returned.
Dependencies
- Requires an API key credential for authenticating with the CrunchzApp API.
- The node sends requests to the base URL:
https://api.crunchz.app/api. - Proper configuration of the API key credential within n8n is necessary for successful operation.
Troubleshooting
Common issues:
- Invalid or missing Contact Id: Ensure the Contact Id is provided in the correct format (
xxx@c.us). - Authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
- Network or API downtime: Check connectivity and CrunchzApp service status.
- Invalid or missing Contact Id: Ensure the Contact Id is provided in the correct format (
Error messages:
- Unauthorized or 401 errors indicate problems with API authentication; recheck credentials.
- 404 errors may mean the specified contact or chat does not exist or is already unarchived.
- Validation errors usually point to incorrect input parameters; verify the Contact Id format.
Links and References
- CrunchzApp API Documentation (assumed based on base URL)
- n8n documentation on API Credentials