Actions64
- Instance Actions
- Message Actions
- Group Actions
- Integration Actions
- Chat Actions
- Profile Actions
- Event Actions
Overview
The node "Evolution API" provides an interface to interact with the Evolution API, allowing users to perform various operations on different resources. Specifically, for the Chat resource and the Edit Message operation, this node enables editing an existing chat message by specifying the contact, message ID, and new message text. This is useful in scenarios where a user needs to update or correct a previously sent message programmatically.
Practical examples include:
- Correcting typos or errors in sent messages.
- Updating information in a chat conversation dynamically.
- Automating message updates based on external triggers or workflows.
Properties
| Name | Meaning |
|---|---|
| Instance Name | The name of the Evolution API instance to use for the request. |
| Contact | The contact number (remote JID) identifying the recipient or chat where the message is. |
| Message ID | The unique identifier of the message that needs to be edited. |
| New Message | The new text content that will replace the original message text. |
Output
The node outputs a JSON array containing the response from the Evolution API after attempting to edit the message. The structure of the JSON output depends on the API's response but typically includes confirmation of the update or details about the edited message.
If the API supports binary data (e.g., media attachments), it would be handled accordingly, but based on the provided code and properties, the focus is on textual message editing.
Dependencies
- Requires an active connection to the Evolution API service.
- Needs an API authentication credential configured in n8n (referred generically as an API key or token).
- Network access to
https://doc.evolution-api.com/api-referenceor the actual Evolution API endpoint.
Troubleshooting
- Operation not supported error: If the specified operation or resource is not implemented, the node throws an error indicating unsupported operation. Ensure the resource and operation names are correct.
- Missing required parameters: All input properties (
Instance Name,Contact,Message ID,New Message) are mandatory. Omitting any will cause execution failure. - API authentication issues: Invalid or missing API credentials will result in authorization errors. Verify the API key/token configuration.
- Invalid message ID or contact: Providing incorrect identifiers may cause the API to return errors or fail silently. Double-check these values.
- Network connectivity problems: Ensure the n8n instance has internet access and can reach the Evolution API endpoints.
Links and References
- Evolution API Documentation (official API reference)
- n8n documentation on creating custom nodes