Actions76
- Message Actions
- Chat Actions
- Contact Actions
- Group Actions
- Create
- List
- Get
- Delete
- Join
- Get Join Info
- Leave
- Get Picture
- Set Picture
- Delete Picture
- Update Subject
- Update Description
- Get Security Info Admin Only
- Set Security Info Admin Only
- Get Security Messages Admin Only
- Set Security Messages Admin Only
- Get Participants
- Add Participant
- Remove Participant
- Promote Admin
- Demote Admin
- Status Actions
- Channel Actions
- Poll Actions
- Profile Actions
- LID Actions
- File Actions
Overview
The "Mark Messages Read" operation in the Chat resource allows users to mark multiple messages as read in a specified chat on WhatsApp via the Wappfy API. This batch operation is useful for automating message management, ensuring that messages up to a certain count or within a recent time frame are marked as read without manually opening each message.
Common scenarios:
- Automatically marking recent messages as read after processing them in an automation workflow.
- Keeping chat statuses updated by marking older unread messages as read in bulk.
- Managing high-volume chats where manual marking would be inefficient.
Practical example:
You have a customer support chat and want to mark the last 30 messages from the past week as read once your system has processed them, preventing repeated notifications or alerts.
Properties
| Name | Meaning |
|---|---|
| Chat ID | The unique identifier of the chat where messages will be marked as read. |
| Messages Count | Number of recent messages to mark as read (default is 30). |
| Days | Time window in days to consider messages for marking as read (default is 7 days). |
Output
The node outputs the response from the Wappfy API after attempting to mark messages as read. The output is a JSON object representing the result of the operation, which typically includes status information about the success or failure of the request.
If multiple input items are processed, the output is an array of JSON objects corresponding to each item.
No binary data output is involved in this operation.
Dependencies
Requires a valid connection to the Wappfy API with proper credentials including:
- Base URL of the Wappfy API instance.
- Instance name identifying the WhatsApp session.
- An API key credential for authentication.
The node must be configured with these credentials in n8n before use.
Troubleshooting
Common issues:
- Invalid or missing Chat ID: The API call will fail if the chat identifier is incorrect or not provided.
- Insufficient permissions or invalid API key: Authentication errors may occur if the API key is invalid or lacks required permissions.
- Network or connectivity problems: Failure to reach the Wappfy API endpoint will cause errors.
Error messages:
"Chat not found"or similar indicates the Chat ID does not exist or is inaccessible."Unauthorized"or"Invalid API key"suggests credential issues.- Timeout or network errors indicate connectivity problems.
Resolutions:
- Verify the Chat ID format and existence.
- Check and update API credentials in n8n.
- Ensure network access to the Wappfy API endpoint.
Links and References
- Wappfy API Documentation (general reference for API endpoints)
- WhatsApp Business API Overview (for understanding WhatsApp messaging concepts)
This summary is based on static analysis of the node's source code and property definitions related to the "Chat" resource and "Mark Messages Read" operation.