Actions50
- Message Actions
- Contact Actions
- Account Actions
- Call Actions
- Chat Actions
- Group Actions
- Instance Actions
- Media Actions
- Session Actions
- User Actions
Overview
This node interacts with the WSAPI WhatsApp API to perform various message-related operations. Specifically, the Delete for Me operation allows a user to delete a WhatsApp message from their own view without removing it for other participants in the chat.
Common scenarios where this node is beneficial include:
- Removing messages from your chat history that you no longer want to see.
- Cleaning up personal message clutter without affecting other users.
- Automating message management workflows where certain messages should be deleted locally after processing.
For example, after receiving and processing a notification message, you might want to delete it from your WhatsApp client using this operation.
Properties
| Name | Meaning |
|---|---|
| To | The WhatsApp contact ID or group ID where the message exists. For contacts, use the phone number followed by @s.whatsapp.net (e.g., 1234567890@s.whatsapp.net). For groups, use the group ID followed by @g.us (e.g., 120363123456789@g.us). The phone number must include the country code but without the plus sign. |
| Message ID | The unique identifier of the WhatsApp message to delete for yourself. This ID can be obtained from previous WhatsApp operations or webhook events. Example: BAE5F2C9A4B1E3D2F7G8H9I0. |
Output
The node outputs a JSON object representing the result of the delete operation. Typically, this will confirm whether the deletion was successful or provide error details if it failed.
No binary data output is expected from this operation.
Dependencies
- Requires an active connection to the WSAPI WhatsApp API service.
- Requires an API key credential configured in n8n to authenticate requests to the WSAPI endpoint.
- The base URL for the WSAPI service must be set in the credentials configuration.
Troubleshooting
- Invalid "To" format: Ensure the contact or group ID is correctly formatted with the appropriate suffix (
@s.whatsapp.netfor contacts,@g.usfor groups) and includes the country code without the plus sign. - Message ID not found: The message ID must be valid and correspond to a message visible to the authenticated user. Use IDs from prior operations or webhook events.
- Authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
- Operation not implemented: If the node throws an error about the operation not being implemented, ensure you are using the latest version of the node and that the operation name matches exactly.
- Network issues: Check connectivity to the WSAPI base URL and ensure no firewall or proxy is blocking requests.
Links and References
- WSAPI WhatsApp API Documentation (example placeholder link; replace with actual WSAPI docs if available)
- WhatsApp message ID format and usage guidelines (refer to official WhatsApp Business API documentation)
- n8n documentation on creating and using custom nodes and credentials