Actions148
- Send messages Actions
- Outbound Messages Actions
- WhatsApp Numbers Actions
- Groups Actions
- Channels Actions
- Chats Actions
- Chat Contacts Actions
- Chat Messages Actions
- Chat Files Actions
- Team Actions
- Labels Actions
- Departments Actions
- Files 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
Overview
This node interacts with the Wassenger WhatsApp API to update chat attributes for a specified WhatsApp number and chat. It allows users to modify metadata of chats such as pinning or muting them. This is useful in scenarios where automated workflows need to organize or prioritize conversations, for example:
- Pinning important customer support chats to keep them visible.
- Muting less urgent group chats during off-hours.
- Automating chat management based on business rules or events.
Properties
| Name | Meaning |
|---|---|
| WhatsApp Number | The ID of the WhatsApp number (device) to operate on. This identifies which WhatsApp account to use. |
| Chat ID | The unique identifier of the chat to update. Examples: 447362053576@c.us for individual user chats, 44736205357600000000@g.us for groups. |
| Attributes | Collection of chat attributes to update: - Pinned: Boolean to pin ( true) or unpin (false) the chat.- Muted: Boolean to mute ( true) or unmute (false) the chat. |
Output
The node outputs JSON data representing the result of the update operation. Typically, this will include confirmation of the updated chat attributes or any relevant response from the Wassenger API indicating success or failure.
No binary data output is produced by this operation.
Dependencies
- Requires an active Wassenger WhatsApp API connection authenticated via an API key credential configured in n8n.
- The node depends on the Wassenger API endpoints related to chat management.
- Proper permissions on the WhatsApp number (device) are necessary to perform chat attribute updates.
Troubleshooting
Common Issues:
- Invalid or missing WhatsApp number (device) ID can cause failures.
- Incorrect chat ID format may lead to "chat not found" errors.
- Insufficient permissions or expired API keys will result in authentication errors.
- Attempting to update attributes on unsupported chat types might fail.
Error Messages:
"Chat not found": Verify the chat ID is correct and belongs to the specified WhatsApp number."Unauthorized"or"Invalid API key": Check that the API key credential is valid and has required access."Failed to update chat attributes": Could indicate network issues or invalid attribute values; review input parameters.
Resolution Tips:
- Double-check all IDs and credentials.
- Ensure the WhatsApp number is active and linked properly.
- Use the node's error output (if continueOnFail is enabled) to debug specific cases.
Links and References
- Wassenger Official API Documentation
- WhatsApp Chat Identifiers Format
- n8n Documentation on Creating Custom Nodes