Evolution API icon

Evolution API

Interact with Evolution API

Overview

The node "Evolution API" allows interaction with the Evolution API service, providing various operations grouped by resources. Specifically, for the resource Chat and operation Editar Mensagem (Edit Message), it enables users to update the text content of an existing chat message. This 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 customer support message.
  • Updating appointment details in a chat conversation.
  • Modifying automated notification messages after they have been sent.

Properties

Name Meaning
Nome Da Instância The name of the instance to connect to the Evolution API service.
Contato The contact number (remote JID) identifying the recipient whose message will be edited.
ID Da Mensagem The unique identifier of the message that is to 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 generally includes confirmation of the updated message status or details about the edited message.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authenticating with the Evolution API.
  • The node expects the Evolution API base URL https://doc.evolution-api.com/api-reference.
  • Proper configuration of the API credentials within n8n is necessary for successful requests.

Troubleshooting

  • Operation not supported error: If the selected operation or resource is not implemented, the node throws an error indicating unsupported operation. Ensure the correct resource ("chat-api") and operation ("update-message") are selected.
  • Missing required parameters: All input properties (Nome Da Instância, Contato, ID Da Mensagem, Nova Mensagem) are mandatory. Omitting any will likely cause request failures.
  • API authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
  • Invalid message ID or contact: If the message ID or contact number does not exist or is incorrect, the API may return an error. Double-check these values before execution.

Links and References

Discussion