Actions83
- 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 retrieving conversations that were previously hidden or closed. For example, if a user accidentally archives an important chat and wants to continue the conversation, this node can be used to unarchive it.
Properties
| Name | Meaning |
|---|---|
| Id | Instance ID (a required numeric identifier for the instance) |
| Chat Id | The unique identifier of the chat to unarchive, typically formatted like <xxxxx>@c.us |
Output
The node outputs JSON data representing the response from the WaAPI API after attempting to unarchive the specified chat. This output typically includes confirmation of the unarchiving action and any relevant metadata about the chat's new state. There is no indication that binary data is returned.
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 key credential within n8n is necessary for successful operation.
Troubleshooting
Common issues:
- Invalid or missing API key credential will cause authentication failures.
- Providing an incorrect or malformed Chat Id may result in errors or no action taken.
- Network connectivity problems can prevent communication with the WaAPI endpoint.
Error messages:
- Authentication errors typically indicate invalid credentials; verify and update the API key.
- "Chat not found" or similar errors suggest the Chat Id does not exist or is incorrect.
- Timeout or connection errors imply network issues; check internet access and endpoint availability.
Links and References
- WaAPI Official Documentation (for detailed API usage and chat management)
- n8n Documentation on Using API Credentials