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 a WhatsApp API service to mark a chat as "seen." When you send a "seen" status for a chat, it indicates that the messages in that chat have been read. This is useful in automation workflows where you want to update message statuses programmatically, such as acknowledging receipt of messages or triggering follow-up actions after reading.
Practical examples include:
- Automatically marking incoming customer support chats as read once processed.
- Syncing read receipts between different systems.
- Automating message handling workflows where read status triggers other operations.
Properties
| Name | Meaning |
|---|---|
| Id | Instance ID (a numeric identifier for the API instance or session). |
| Chat Id | The unique identifier of the chat to mark as seen. Format: <countrycode><usernumber>@c.us for individual chats or @g.us for groups. |
Output
The node outputs JSON data representing the response from the WhatsApp API after sending the "seen" status. This typically includes confirmation of the action or any relevant metadata returned by the API.
No binary data output is involved.
Dependencies
- Requires an active connection to the WhatsApp API service at
https://waapi.app/api/v1. - Needs an API key credential configured in n8n to authenticate requests to the WhatsApp API.
- The node uses standard HTTP headers for JSON content type and expects JSON responses.
Troubleshooting
- Invalid Chat Id format: Ensure the chat ID follows the correct pattern (
<countrycode><usernumber>@c.usfor individuals or@g.usfor groups). - Authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
- Network issues: Confirm that the n8n instance can reach the WhatsApp API endpoint.
- API rate limits: If too many requests are sent in a short time, the API might reject further calls temporarily.
- Instance ID errors: Make sure the provided instance ID corresponds to a valid and active session on the WhatsApp API.
Links and References
- WhatsApp API Documentation (for detailed API usage and chat ID formats)
- n8n Documentation (for general node usage and credential setup)