Actions148
- Chats Actions
- Chat Contacts Actions
- Chat Messages Actions
- Chat Files Actions
- Files Actions
- Team Actions
- Labels Actions
- Departments Actions
- Quick replies Actions
- Queue Actions
- WhatsApp session Actions
- WhatsApp profile Actions
- Business catalog Actions
- Campaigns Actions
- Meeting Links Actions
- User Status Actions
- Webhooks Actions
- Other Actions
- Send messages Actions
- Outbound Messages Actions
- WhatsApp Numbers Actions
- Groups Actions
- Channels Actions
Overview
The "Archive Chat" operation under the "Chats" resource allows users to archive a specific WhatsApp chat associated with a given WhatsApp number. Archiving a chat typically means marking it as archived in the WhatsApp system, which can help organize conversations by hiding them from the main chat list without deleting them.
This node operation is beneficial for automating chat management workflows, such as:
- Automatically archiving chats after they are resolved or inactive.
- Organizing chats programmatically based on custom business logic.
- Integrating WhatsApp chat status updates into broader CRM or support systems.
For example, a customer support team could use this operation to archive chats once a ticket is closed, keeping their active chat list clean.
Properties
| Name | Meaning |
|---|---|
| WhatsApp Number | The ID of the WhatsApp number (device) to operate on. This identifies which WhatsApp account to use. Options are dynamically loaded from available devices. |
| Chat ID | The unique identifier of the chat to archive. Examples include user chats like 447362053576@c.us or group chats like 44736205357600000000@g.us. |
Output
The output JSON contains the response from the API call that archives the specified chat. It typically includes confirmation details about the archived chat, such as its ID and status. The exact structure depends on the underlying API response but generally confirms successful archiving.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the SparkBot WhatsApp API.
- The node depends on the availability of registered WhatsApp numbers (devices) to select from.
- Proper configuration of the API key credential within n8n is necessary for successful execution.
Troubleshooting
Common Issues:
- Invalid or missing WhatsApp number (device) selection may cause failures.
- Incorrect or malformed Chat ID will result in errors from the API.
- Network or authentication issues with the SparkBot API can prevent archiving.
Error Messages:
- Errors related to authorization usually indicate problems with the API key credential; verify and update credentials as needed.
- "Chat not found" or similar messages suggest the provided Chat ID does not exist or is inaccessible for the selected device.
- Rate limiting or API quota exceeded errors require checking API usage limits.
Resolving these typically involves verifying input parameters, ensuring valid credentials, and confirming the chat exists on the specified WhatsApp number.
Links and References
- SparkBot WhatsApp API Documentation (general reference for API capabilities)
- WhatsApp Chat Identifiers Format (explains chat ID formats for users and groups)