Actions53
- Instância Actions
- Mensagem Actions
- Grupo Actions
- Chat Actions
- Evento Actions
- Integração Actions
Overview
This node integrates with the Evolution API v2 to perform various operations related to WhatsApp messaging and instance management. Specifically, for the Chat resource and the "Marcar como Não lido" (Mark as Unread) operation, it allows users to mark a message as unread in a specified WhatsApp chat instance.
Common scenarios where this node is beneficial include:
- Automating message status management in customer support workflows.
- Integrating WhatsApp message handling into CRM or helpdesk systems.
- Managing read/unread states programmatically to trigger follow-ups or notifications.
For example, after processing a message automatically, you might want to mark it as unread to alert a human agent to review it later.
Properties
| Name | Meaning |
|---|---|
| Instance Name | The name of the WhatsApp instance where the chat/message exists. This identifies which connected WhatsApp session to operate on. |
Output
The node outputs JSON data representing the result of the API call. The output includes:
success: A boolean indicating if the operation was successful.message: A success message string (if applicable).timestamp: The ISO timestamp when the operation was completed.- Additional fields returned by the Evolution API depending on the specific operation.
If the API returns an array of items, these are parsed and included in the output as an array under items, along with count indicating the number of items.
The node does not output binary data for this operation.
Dependencies
- Requires an API key credential configured in n8n to authenticate requests to the Evolution API.
- The Evolution API v2 must be accessible from the n8n environment.
- Proper configuration of the WhatsApp instance within the Evolution platform is necessary.
Troubleshooting
Common issues:
- Incorrect or missing instance name will cause the API call to fail.
- Network connectivity problems between n8n and the Evolution API endpoint.
- Insufficient permissions or invalid API credentials can lead to authentication errors.
Error messages:
- Errors thrown by the node typically contain the API error message.
- If the node fails due to invalid JSON input or unexpected response format, ensure that all parameters are correctly set.
- To handle errors gracefully, enable "Continue On Fail" in the node settings.
Links and References
- Evolution API Documentation (hypothetical link, replace with actual if available)
- n8n documentation on Creating Custom Nodes
- WhatsApp Business API concepts for message status management
Note: The above summary focuses on the Chat resource's "Mark as Unread" operation based on the provided source code and property definitions.