Actions64
- Instancia Actions
- Mensaje Actions
- Grupo Actions
- Crear Grupo
- Actualizar Imagen Del Grupo
- Actualizar Nombre Del Grupo
- Actualizar Descripción Del Grupo
- Actualizar Configuraciones
- Actualizar Miembros
- Buscar Enlace De Invitación
- Revocar Enlace De Invitación
- Enviar Enlace De Invitación
- Buscar Grupos
- Encontrar Participantes
- Mensajes Temporales
- Unirse Al Grupo
- Salir Del Grupo
- Chat Actions
- Perfil Actions
- Evento Actions
- Integración Actions
Overview
The node "Evolution API" provides an interface to interact with the Evolution API service. Specifically, for the Resource "Chat" and Operation "Editar Mensaje" (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 chat content by editing messages post-sending.
Properties
| Name | Meaning |
|---|---|
| Nombre De La Instancia | The name of the Evolution API instance to use for the operation. |
| Contacto | The contact number (remote JID) identifying the recipient or chat where the message exists. |
| ID Del Mensaje | The unique identifier of the message that will be edited. |
| Nuevo Mensaje | 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 message update or details about the updated message.
No binary data output is indicated.
Dependencies
- Requires an API key credential for the Evolution API configured in n8n.
- The node uses the base URL
https://doc.evolution-api.com/api-referencefor API requests. - Proper configuration of the instance name and valid contact/message IDs are necessary for successful execution.
Troubleshooting
- Operation not supported error: If the specified resource-operation combination is not implemented, the node throws an error indicating unsupported operation. Ensure the resource is "chat-api" and operation is "update-message".
- Invalid or missing parameters: Missing required properties like instance name, contact number, message ID, or new message text will cause failures. Verify all required inputs are provided.
- API authentication issues: Incorrect or missing API credentials will prevent communication with the Evolution API.
- Message ID not found: If the message ID does not exist or is invalid, the API may return an error. Confirm the message ID corresponds to an existing message.
- Network or API errors: Connectivity problems or API downtime can cause request failures.
Links and References
- Evolution API Documentation (base URL used by the node)
- n8n documentation on Creating Custom Nodes