Evolution API Direct icon

Evolution API Direct

Interact with Evolution API using direct URL and API Key

Actions64

Overview

The node "Evolution API Direct" allows users to interact with the Evolution API by specifying a direct server URL and an API key. It supports various resources and operations, including editing chat messages. This node is useful for automating message updates in chat systems powered by the Evolution API, such as correcting or updating sent messages without resending them.

A practical example is when a user wants to update the content of a previously sent chat message identified by its message ID and contact number. The node sends the new text to the API, which edits the existing message accordingly.

Properties

Name Meaning
Server URL The full URL of your Evolution API server endpoint (e.g., https://api.exemplo.com).
API Key The API key credential required to authenticate requests to the Evolution API instance.
Nome Da Instância The name of the specific Evolution API instance you want to target.
Contato The contact number (remote JID) associated with the chat message to be edited.
ID Da Mensagem The unique identifier of the message that will be edited.
Nova Mensagem 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 depends on the API's response but typically includes confirmation of the update or error details if the operation failed.

No binary data output is indicated.

Dependencies

  • Requires access to the Evolution API via a valid server URL.
  • Requires an API key credential for authentication.
  • Needs the name of the Evolution API instance to target.
  • The node relies on n8n's HTTP request capabilities to communicate with the API.

Troubleshooting

  • Common Issues:

    • Incorrect or missing API key leading to authentication failures.
    • Invalid server URL causing connection errors.
    • Wrong message ID or contact number resulting in failure to locate the message.
    • Insufficient permissions on the API key to perform message edits.

  • Error Messages:

    • "Operação não suportada." indicates the requested operation is not implemented for the selected resource.
    • Network or timeout errors suggest connectivity issues with the provided server URL.
    • API errors returned in the JSON response should be checked for detailed causes, such as invalid parameters or authorization problems.

  • Resolutions:

    • Verify the API key and ensure it has the necessary rights.
    • Confirm the server URL is correct and reachable.
    • Double-check the message ID and contact number for accuracy.
    • Review API documentation for any additional required parameters or constraints.

Links and References

Discussion