Actions64
- Instance Actions
- Message Actions
- Group Actions
- Chat Actions
- Profile Actions
- Event Actions
- Integration Actions
Overview
The node "Evolution API" provides an interface to interact with the Evolution API service. Specifically, for the Resource "Chat" and Operation "Edit Message," it allows users to update the text content of an existing chat message by specifying the instance, contact, message ID, and new message text. This is useful in scenarios where a sent message needs correction or updating without sending a new message.
Practical examples include:
- Correcting typos or errors in previously sent messages.
- Updating information in a message after receiving new data.
- Moderating or managing chat conversations programmatically.
Properties
| Name | Meaning |
|---|---|
| Name Da Instância | The name of the instance where the chat is hosted or managed. |
| Contato | The contact number (remote JID) identifying the recipient or chat participant. |
| Message ID | The unique identifier of the message that will be edited. |
| 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. The exact structure depends on the Evolution API response but typically includes confirmation of the updated message or status information.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Evolution API.
- The node uses the base URL
https://doc.evolution-api.com/api-referencefor API requests. - Proper configuration of the API authentication credentials within n8n is necessary.
Troubleshooting
- Operation Not Supported Error: If the specified resource-operation combination is not supported, the node throws an error indicating the operation is unsupported. Ensure the correct resource ("chat-api") and operation ("update-message") are selected.
- Missing Required Parameters: All input properties are required; missing any will cause execution failure. Verify all fields like instance name, contact number, message ID, and new message text are provided.
- API Authentication Issues: Invalid or missing API credentials will prevent successful communication with the Evolution API. Confirm that the API key credential is correctly set up.
- Message Not Found: If the message ID does not exist or is incorrect, the API may return an error. Double-check the message ID value.
Links and References
- Evolution API Documentation (base URL used by the node)