Actions29
- Sessions Actions
- Chats Actions
- Contacts Actions
- Groups Actions
- Messages Actions
Overview
This node integrates with a WhatsApp HTTP API to manage messages. Specifically, the "Delete Message" operation under the "Messages" resource allows users to delete a message associated with a particular phone session. This is useful in scenarios where you want to programmatically remove messages from a WhatsApp session, such as cleaning up chat history or retracting sent messages.
Practical examples include:
- Automatically deleting messages after a certain workflow step completes.
- Removing sensitive information sent by mistake.
- Managing message lifecycle in customer support automation.
Properties
| Name | Meaning |
|---|---|
| Phone | The phone number (session ID) associated with the WhatsApp session where the message will be deleted. Defaults to the phone number credential used for authentication. |
Output
The node outputs JSON data representing the result of the delete message operation. This typically includes confirmation of deletion or any error details returned by the WhatsApp API. There is no indication that binary data is output by this node.
Dependencies
- Requires connection to a WhatsApp HTTP API service.
- Needs an API key or authentication token configured via credentials in n8n.
- The base URL for the WhatsApp API must be set in the node's credentials.
- Uses the
@devlikeapro/n8n-openapi-nodepackage for OpenAPI integration.
Troubleshooting
Common issues:
- Invalid or missing phone session ID can cause the delete operation to fail.
- Incorrect or expired API credentials will prevent successful communication with the WhatsApp API.
- Network connectivity problems may lead to timeouts or unreachable errors.
Error messages:
- Authentication errors usually indicate invalid API keys or tokens; verify and update credentials.
- "Message not found" errors suggest the specified message or session does not exist; confirm the session ID and message identifiers.
- API rate limits might cause temporary failures; consider adding retry logic or checking API usage quotas.