Evolution API icon

Evolution API

Interact with Evolution API
Join our community

Actions64

Overview

The node "Evolution API" provides an interface to interact with the Evolution API, specifically supporting operations on various resources. For the resource "Chat" and operation "Editar Mensagem" (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 node is beneficial in scenarios where automated or programmatic editing of chat messages is required, such as correcting typos, updating information, or managing conversations dynamically within a messaging platform integrated via the Evolution API.

Example use cases:

  • Automatically correcting a previously sent message in a customer support chat.
  • Updating notification messages with new data without sending a new message.
  • Managing chat content in bulk through workflows.

Properties

Name Meaning
Nome Da Instância The name of the Evolution API instance to connect to.
Contato The contact number (remote JID) identifying the chat recipient whose message will be edited.
ID Da Mensagem The unique identifier of the message that needs to 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 corresponds to the response from the Evolution API after attempting to update the specified message. The exact structure depends on the API's response but generally 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 purely JSON-based.

Dependencies

  • Requires an active connection to the Evolution API, authenticated via an API key credential configured in n8n.
  • The node depends on the Evolution API service being available and accessible.
  • Proper configuration of the instance name and valid identifiers for contacts and messages are necessary.

Troubleshooting

  • Operation Not Supported 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.
  • Invalid Credentials: Authentication failures may occur if the API key or credentials are missing or incorrect. Ensure the API key credential is properly configured.
  • Message Not Found: Errors related to the message ID usually indicate that the specified message does not exist or is inaccessible. Double-check the message ID and contact number.
  • Network Issues: Connectivity problems with the Evolution API can cause timeouts or failed requests. Verify network access and API endpoint availability.
  • Empty or Invalid Input: Required fields like instance name, contact, message ID, and new message text must be provided and valid; otherwise, the node will fail.

Links and References

Discussion