Evolution API

Interagir com a Evolution API v2
Join our community

Actions53

Overview

This node integrates with the Evolution API v2 to send WhatsApp messages and perform related messaging operations. Specifically, for the "Mensagem" resource and the "Enviar Texto" operation, it sends a plain text message to a specified recipient number via a selected instance.

Common scenarios where this node is useful include automating customer notifications, sending alerts or reminders, and integrating WhatsApp messaging into workflows without manual intervention.

For example, you can use this node to automatically send order confirmations or support updates to customers on WhatsApp by specifying the instance name, recipient number, and message text.

Properties

Name Meaning
Instance Name The name of the Evolution API instance through which the message will be sent.
Number The recipient's phone number in international format to which the text message will be sent.
Message Text The content of the text message to be sent to the recipient.

Output

The node outputs a JSON object containing the response from the Evolution API after attempting to send the message. The output includes:

  • success: A boolean indicating if the operation was successful.
  • timestamp: The ISO string timestamp when the operation completed.
  • Additional fields returned by the API response, which may include message IDs or status details depending on the API.

If the API returns no data, the node outputs a generic success message with a timestamp.

No binary data output is produced by this operation.

Dependencies

  • Requires an active Evolution API v2 credential configured in n8n for authentication.
  • The node makes HTTP requests to the Evolution API endpoints.
  • The user must have a valid instance created and connected in the Evolution system to send messages.

Troubleshooting

  • Common issues:

    • Invalid or missing instance name: Ensure the instance name matches an existing and connected Evolution API instance.
    • Incorrect recipient number format: Use the international phone number format without spaces or special characters.
    • API authentication errors: Verify that the API key or credentials are correctly set up in n8n.
    • Network or connectivity problems: Check that the Evolution API service is reachable from your environment.

  • Error messages:

    • Errors thrown by the API (e.g., unauthorized, not found) will be surfaced as error messages in the node output.
    • If the node is set to continue on fail, errors will appear in the output JSON under an error field.
    • To resolve, verify credentials, input parameters, and network connectivity.

Links and References

Discussion