Actions64
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
- Instancia Actions
- Mensagem Actions
- Grupo Actions
Overview
The node provides an interface to interact with the "Evolution API," specifically supporting operations on various resources. For the Chat resource, the Delete Message operation allows users to delete a specific message from a chat instance. This is useful in scenarios where you want to programmatically remove messages sent or received by a particular contact or participant, such as cleaning up chat history, retracting sent messages, or managing chat content automatically.
Practical examples include:
- Automatically deleting sensitive messages after a certain event.
- Removing erroneous or duplicate messages from a conversation.
- Managing chat logs by deleting messages based on custom business rules.
Properties
| Name | Meaning |
|---|---|
| Nome Da Instância | The name of the chat instance where the message exists. |
| Contato | The contact number (remote JID) associated with the chat where the message will be deleted. |
| ID Da Mensagem | The unique identifier of the message to be deleted. |
| Mensagem É Minha | Boolean indicating if the message was sent by the instance itself (true) or not (false). |
| Número Do Participante | The number of the participant who sent the message; required only if the message is not from the instance. |
Output
The node outputs a JSON array containing the result of the delete message operation. Typically, this output would confirm whether the deletion was successful or provide details about the deleted message. The exact structure depends on the Evolution API response but generally includes status or confirmation fields.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential to authenticate with the Evolution API.
- The node expects proper configuration of the Evolution API credentials within n8n.
- Network access to the Evolution API endpoint is necessary.
Troubleshooting
- Operation Not Supported Error: If the node throws an error stating the operation is not supported, verify that the resource and operation names are correctly set to "chat" and "delete-message" respectively.
- Missing Required Parameters: Ensure all required properties (instance name, contact number, message ID, fromMe flag, and participant number when applicable) are provided.
- Authentication Failures: Confirm that the API key credential is valid and has sufficient permissions to delete messages.
- Message Not Found: If the message ID does not exist or is incorrect, the API may return an error. Double-check the message ID.
- Permission Issues: Deleting messages not sent by the instance might require additional permissions or specifying the correct participant number.
Links and References
- Evolution API official documentation (link not provided in source)
- n8n documentation on creating and using API nodes: https://docs.n8n.io/integrations/creating-nodes/
- General best practices for chat message management APIs