Evolution API icon

Evolution API

Interact with Evolution API

Actions64

Overview

The node named "Evolution API" provides an interface to interact with the Evolution API service. Specifically, for the Chat resource and the Edit Message operation, it allows users to update the text content of an existing chat message by specifying the contact, message ID, and new message text.

This node is beneficial in scenarios where automated workflows need to modify previously sent messages, such as correcting typos, updating information, or dynamically changing message content based on external triggers or conditions.

Example use case:

  • A customer support automation that edits a sent message to add additional details after receiving more information from a backend system.
  • Updating notification messages in a chat when the status of an order changes.

Properties

Name Meaning
Instance Name The name of the Evolution API instance to connect to.
Contact The identifier (contact number) of the recipient whose message is to be edited.
Message ID The unique identifier of the message that needs to be updated.
New Message The new text content that will replace the original message's text.

Output

The node outputs a JSON array containing the response from the Evolution API after attempting to edit the message. This typically includes confirmation of the update or details about the updated message. The exact structure depends on the API response but generally confirms success or failure of the edit operation.

No binary data output is indicated.

Dependencies

  • Requires an active connection to the Evolution API service.
  • Needs an API authentication credential configured in n8n to authorize requests.
  • The base URL for the API is https://doc.evolution-api.com/api-reference.
  • The node expects JSON-formatted requests and responses.

Troubleshooting

  • Unsupported operation error: If the specified operation or resource is not supported, the node throws an error indicating this. Ensure the resource is set to "chat-api" and operation to "update-message" for editing messages.
  • Missing required parameters: All properties (Instance Name, Contact, Message ID, New Message) are required. Omitting any will likely cause the API call to fail.
  • API authentication errors: Verify that the API key or authentication token is correctly configured and has sufficient permissions.
  • Invalid message ID or contact: If the message ID or contact does not exist or is incorrect, the API may return an error or fail silently. Double-check these values.
  • Network issues: Connectivity problems can cause request failures; ensure the n8n instance has internet access and the API endpoint is reachable.

Links and References

Discussion