Actions85
- Instances Actions
- Client Actions
- Message Actions
- Chat Actions
- Contact Actions
- Number Actions
- Group Actions
- Channel Actions
- Label Actions
- Story Actions
Overview
The node provides an operation to archive a chat in the "Chat" resource. Archiving a chat typically means marking it as archived or hidden from the main chat list without deleting it, which helps users organize their conversations by removing inactive or less important chats from immediate view.
This node is useful in scenarios where you want to automate chat management, such as:
- Automatically archiving chats after a certain period of inactivity.
- Archiving chats based on specific triggers or events in your workflow.
- Managing chat visibility programmatically in bulk operations.
For example, you could use this node to archive customer support chats once the issue is resolved, keeping the chat interface clean and focused on active conversations.
Properties
| Name | Meaning |
|---|---|
| Id | Instance ID (a required numeric identifier for the instance context). |
| Chat Id | The unique identifier of the chat to be archived, typically formatted like <xxxxx>@c.us. |
Output
The node outputs JSON data representing the result of the archive chat operation. This output typically includes confirmation that the chat was successfully archived or details about the updated chat status.
No binary data output is indicated in the source code or properties.
Dependencies
- Requires an API key credential to authenticate with the external WaAPI service.
- The node interacts with the WaAPI API endpoint at
https://waapi.app/api/v1. - Proper configuration of the API authentication credentials within n8n is necessary for successful execution.
Troubleshooting
Common issues:
- Invalid or missing API credentials 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 service.
Error messages and resolutions:
- Authentication errors: Verify that the API key credential is correctly set up and has the necessary permissions.
- Invalid Chat Id: Ensure the Chat Id follows the expected format (e.g.,
<xxxxx>@c.us) and corresponds to an existing chat. - API request failures: Check network connectivity and the availability of the WaAPI service.
Links and References
- WaAPI Official Documentation (for detailed API usage and chat management)
- n8n Documentation (for general guidance on using credentials and HTTP request nodes)