Actions22
- Channel Actions
- Chat Actions
- Message Actions
- Contact Actions
- OTP Code Actions
- OTP Link Actions
Overview
The node interacts with the CrunchzApp API to perform operations related to chat management. Specifically, the "Archive Chat" operation allows users to archive a chat conversation by specifying the contact's unique identifier. This is useful for organizing chats, decluttering active conversations, or marking chats as no longer active without deleting them.
Practical examples include:
- Automatically archiving chats after a support ticket is resolved.
- Archiving old customer conversations to keep the chat list manageable.
- Integrating chat archival into workflows that manage communication lifecycle.
Properties
| Name | Meaning |
|---|---|
| Contact Id | The unique identifier of the contact whose chat will be archived. It follows the format xxx@c.us. |
Output
The node outputs JSON data representing the response from the CrunchzApp API after attempting to archive the specified chat. This typically includes confirmation of the archival action or any relevant status messages. There is no indication that binary data is output by this node.
Dependencies
- Requires an API key credential for authenticating with the CrunchzApp API.
- The node sends requests to the CrunchzApp API endpoint at
https://api.crunchz.app/api. - Proper configuration of the API authentication credential within n8n is necessary.
Troubleshooting
Common issues:
- Invalid or missing Contact Id: Ensure the Contact Id is correctly formatted and corresponds to an existing contact.
- Authentication errors: Verify that the API key credential is valid and has the necessary permissions.
- Network or API downtime: Check connectivity and CrunchzApp service status.
Error messages:
- Authorization failures usually indicate invalid credentials; reconfigure the API key.
- "Contact not found" or similar errors suggest the Contact Id does not exist or is incorrect.
- Unexpected API responses may require checking the CrunchzApp API documentation or contacting support.
Links and References
- CrunchzApp API Documentation (assumed URL based on baseURL)
- n8n Documentation on API Credentials