Evolution API Direct icon

Evolution API Direct

Interact with Evolution API using direct URL and API Key

Actions64

Overview

This node, named "Evolution API Direct," allows users to send text messages through the Evolution API by specifying a direct server URL and an API key. It is designed for scenarios where you want to programmatically send WhatsApp-like text messages to specific recipients using your Evolution API instance.

Typical use cases include:

  • Automating customer support or notifications by sending text messages.
  • Integrating messaging capabilities into workflows that require sending alerts or updates.
  • Sending personalized messages with options such as delays, replies to specific messages, mentions, and link previews.

For example, you can configure this node to send a welcome message to a new user, mention specific participants in a group chat, or reply to a previous message with a delay.

Properties

Name Meaning
Server URL The full URL of your Evolution API server (e.g., https://api.exemplo.com). This is the endpoint where requests will be sent.
API Key The API key for authenticating with your Evolution API instance. This key must be kept secret and is required for authorization.
Nome Da Instancia The name of the Evolution API instance that will send the message.
Numero Do Destinatario The recipient's remote JID (unique identifier for the destination contact). Required to specify who will receive the message.
Mensagem The text content of the message to be sent.
Opções Additional optional settings for the message:
- Delay Number of milliseconds to wait before sending the message. Default is 1200 ms.
- Responder Mensagem Allows replying to a specific message by providing its message ID.
- Menções Settings for mentioning participants in the message: either mention everyone in a group or specify a comma-separated list of numbers to mention.
- Preview De Link Boolean flag to enable or disable link preview in the message. Defaults to enabled (true).

Output

The node outputs a JSON array containing the response from the Evolution API after attempting to send the message. The structure typically includes details about the message delivery status, message ID, timestamps, or error information if the request failed.

If the API supports binary data (e.g., media attachments), this node focuses on text messages only, so no binary output is expected here.

Dependencies

  • Requires access to an Evolution API server reachable via the provided Server URL.
  • Requires a valid API key credential for authentication.
  • The node depends on the Evolution API's availability and correct configuration of the instance name and recipient identifiers.

Troubleshooting

  • Common Issues:

    • Incorrect Server URL or API Key will result in authentication errors or connection failures.
    • Invalid or missing recipient JID (Numero Do Destinatario) will cause the message not to be delivered.
    • Providing an invalid message ID in the reply option may cause the API to reject the request.
    • Network issues or API downtime can prevent message sending.

  • Error Messages:

    • "Operação não suportada." indicates that the selected operation or resource is not implemented or recognized by the node.
    • Authentication errors usually indicate invalid API keys or insufficient permissions.
    • Validation errors may occur if required fields are missing or incorrectly formatted.

  • Resolutions:

    • Verify the Server URL and API Key are correct and active.
    • Ensure the recipient JID is accurate and corresponds to a valid contact.
    • Check the message ID used for replies exists and belongs to the conversation.
    • Confirm network connectivity and API service status.

Links and References

Discussion