Actions85
- Instances Actions
- Client Actions
- Message Actions
- Chat Actions
- Contact Actions
- Number Actions
- Group Actions
- Channel Actions
- Label Actions
- Story Actions
Overview
This node interacts with the WaAPI API to unarchive a specific chat. It is useful in scenarios where archived chats need to be restored to active status, such as when a user wants to resume communication or manage chat visibility dynamically. For example, if a chat was previously archived for organizational purposes but later requires attention, this node can programmatically unarchive it.
Properties
| Name | Meaning |
|---|---|
| Id | Instance ID (a required numeric identifier) |
| Chat Id | The unique identifier of the chat to unarchive (e.g., <xxxxx>@c.us) |
Output
The node outputs JSON data representing the response from the WaAPI API after attempting to unarchive the specified chat. This typically includes confirmation of the unarchive action and any relevant metadata about the chat's new state. There is no indication that binary data is output by this node.
Dependencies
- Requires an API key credential for authenticating with the WaAPI API.
- The node sends requests to
https://waapi.app/api/v1. - Proper configuration of the API authentication credential within n8n is necessary.
Troubleshooting
- Common issues:
- Invalid or missing chat ID may cause the API to reject the request.
- Incorrect or expired API credentials will result in authentication errors.
- Network connectivity problems can prevent reaching the WaAPI endpoint.
- Error messages:
- Authentication failures usually indicate invalid API keys; verify and update credentials.
- "Chat not found" or similar errors suggest the provided chat ID does not exist or is incorrect.
- Timeout or connection errors require checking network access and API availability.
Links and References
- WaAPI Official Documentation (for detailed API usage and chat management)
- n8n Documentation (for general node usage and credential setup)