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 Editar Mensagem (Edit Message) operation, it allows editing an existing message in a WhatsApp chat through the Evolution API.
Common scenarios where this node is beneficial include:
- Updating or correcting sent messages in WhatsApp chats.
- Automating message edits as part of customer support workflows.
- Managing chat content dynamically based on external triggers or data changes.
Practical example:
- A customer support system detects a typo in a previously sent message and uses this node to update the message text without sending a new message.
Properties
| Name | Meaning |
|---|---|
| Instance Name | The name of the Evolution API instance to use for the operation. This identifies which WhatsApp instance the action will be performed on. |
Note: The provided input properties JSON only includes "Instance Name" which is required for all operations across resources including Chat.
Output
The node outputs a JSON array where each item corresponds to the result of processing one input item. The output structure generally includes:
success: Boolean indicating if the operation was successful.messageor other relevant response fields returned by the Evolution API.timestamp: ISO string timestamp when the operation was completed.- Additional fields depend on the specific API response for the edit message operation.
If the API returns multiple items or strings, the node attempts to parse them into JSON objects. If parsing fails, raw values are included.
The node does not explicitly handle binary data for this operation.
Dependencies
- Requires an authenticated connection to the Evolution API v2 via an API key credential configured in n8n.
- The node uses HTTP requests to the Evolution API endpoints.
- Proper configuration of the Evolution API instance name is necessary to target the correct WhatsApp session.
Troubleshooting
Common issues:
- Incorrect or missing instance name can cause failures connecting to the right WhatsApp session.
- Invalid or expired API credentials will prevent successful API calls.
- Editing a message that does not exist or is outside allowed time limits may result in API errors.
Error messages:
- Authentication errors indicate problems with the API key or token; verify credentials.
- "Message not found" or similar errors mean the specified message ID is invalid or no longer editable.
- Network or timeout errors suggest connectivity issues with the Evolution API service.
Resolutions:
- Double-check instance names and ensure the instance is active.
- Renew or reconfigure API authentication tokens.
- Confirm message IDs and timing constraints with the Evolution API documentation.
Links and References
- Evolution API v2 Documentation (hypothetical link as actual URL not provided)
- n8n HTTP Request Node documentation for understanding requestWithAuthentication usage.
- WhatsApp Business API guidelines on message editing limitations.