Actions64
- Instancia Actions
- Mensagem Actions
- Grupo Actions
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
Overview
The node named "Evolution API" is designed to interact with the Evolution API service, providing various operations grouped by resource types. Specifically, for the Chat resource and the Editar Mensagem (Edit Message) operation, this node allows users to update the content of an existing chat message by specifying the instance, contact, message ID, and new text. This functionality is useful in scenarios where a sent message needs correction or updating without sending a new message, such as fixing typos or adding additional information.
Practical examples include:
- Correcting a typo in a previously sent message to a contact.
- Updating a message's content to reflect new information.
- Modifying automated messages sent through the Evolution API integration.
Properties
| Name | Meaning |
|---|---|
| Nome Da Instância | The name of the Evolution API instance to use for the operation. |
| Contato | The contact number (remote JID) identifying the recipient of the message to be edited. |
| ID Da Mensagem | The unique identifier of the message that will be updated. |
| Nova Mensagem | The new text content that will replace the original message text. |
Output
The node outputs a JSON array containing the result of the edit message operation. Each item in the output array corresponds to the response from the Evolution API after attempting to update the specified message. The exact structure depends on the API response but typically includes confirmation of success or details about the updated message.
If the node supports binary data output, it is not indicated in the provided code or properties; thus, the output is expected to be purely JSON-based.
Dependencies
- Requires an API key credential for authenticating with the Evolution API service.
- The node expects the Evolution API endpoint to be accessible and properly configured.
- No additional environment variables are explicitly required based on the provided code.
Troubleshooting
- Unsupported Operation 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-api" and "update-message" respectively.
- Missing Required Parameters: Ensure all required properties (
Nome Da Instância,Contato,ID Da Mensagem,Nova Mensagem) are provided; missing any will likely cause the operation to fail. - API Authentication Issues: Confirm that the API key credential is valid and has the necessary permissions to perform message edits.
- Message Not Found: If the specified message ID does not exist or is incorrect, the API may return an error indicating the message cannot be found or updated.
- Network or Service Errors: Check network connectivity and the status of the Evolution API service if requests time out or fail unexpectedly.
Links and References
- Evolution API Documentation (Replace with actual URL)
- n8n Documentation on Creating Custom Nodes
- General guidance on Handling API Credentials in n8n