Actions22
- Channel Actions
- Chat Actions
- Message Actions
- Contact Actions
- OTP Code Actions
- OTP Link Actions
Overview
This node interacts with the CrunchzApp API to unarchive a chat for a specified contact. It is useful in scenarios where archived chats need to be restored to active status, such as when a user wants to resume communication with a previously archived contact.
For example, if a user has archived a chat with a customer but later needs to continue the conversation, this node can be used to unarchive that chat by providing the contact's ID.
Properties
| Name | Meaning |
|---|---|
| Contact Id | The unique identifier of the contact whose chat should be unarchived. Format example: xxx@c.us. |
Output
The node outputs JSON data representing the response from the CrunchzApp API after attempting to unarchive the chat. This typically includes confirmation of success or details about the updated chat status.
No binary data output is indicated.
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.
Troubleshooting
- Invalid Contact Id: If the provided Contact Id is malformed or does not exist, the API may return an error. Verify the Contact Id format and ensure it corresponds to an existing contact.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key credential is correctly set up.
- Network Issues: Connectivity problems to the CrunchzApp API endpoint can cause request failures. Check network access and API availability.
- API Rate Limits: Excessive requests might be throttled by the API. Review API usage limits and adjust accordingly.
Links and References
- CrunchzApp API Documentation (assumed based on base URL; verify actual documentation link)
- n8n Documentation on Using Credentials