Actions64
- Instance Actions
- Message Actions
- Group Actions
- Chat Actions
- Profile Actions
- Event Actions
- Integration Actions
Overview
The node "Evolution API" allows users to send text messages through the Evolution messaging platform. It is designed to interact with the Evolution API, enabling automated sending of text messages to specified recipients. This node is useful in scenarios such as customer support automation, notification systems, or any workflow requiring programmatic message dispatch.
For example, you can use this node to send a welcome message to new users, notify team members about system alerts, or reply automatically to incoming messages.
Properties
| Name | Meaning |
|---|---|
| Instance Name | The name of the Evolution API instance that will send the message. |
| Recipient Number | The recipient's remoteJid (unique identifier for the recipient). Required field. |
| Message | The text content of the message to be sent. Required field. |
| Options: | A collection of optional settings to customize message sending: |
| - Delay | Delay in milliseconds before the message is sent (default 1200 ms). |
| - Reply to Message | ID of a message to which this message should be a reply (quoted message). |
| - Mentions | Settings to mention participants in the message: |
| • Mention Everyone: Boolean to mention all group participants. | |
| • Numbers to Mention: Comma-separated list of numbers to mention individually (if not mentioning everyone). | |
| - Link Preview | Boolean to enable or disable link preview in the message (default enabled). |
Output
The node outputs an array of JSON objects representing the result of the send text operation. Each object corresponds to the response from the Evolution API after attempting to send a message. The exact structure depends on the API response but generally includes status and message metadata.
No binary data output is indicated by the source code.
Dependencies
- Requires an active Evolution API credential configured in n8n to authenticate requests.
- Depends on the Evolution API service being accessible at
https://doc.evolution-api.com/api-reference. - No other external dependencies are indicated.
Troubleshooting
- Unsupported operation error: If the node throws an error stating the operation is unsupported, verify that the resource is set to "messages-api" and the operation to "send-text".
- Missing required fields: Ensure that "Recipient Number" and "Message" properties are provided; otherwise, the node will fail.
- API authentication issues: Confirm that the Evolution API credentials are correctly configured and valid.
- Delay misconfiguration: Setting an excessively high delay may cause unexpected workflow timing; use reasonable values.
- Mention formatting errors: When specifying individual numbers to mention, ensure they are comma-separated without extra spaces or invalid characters.
Links and References
- Evolution API Documentation (base URL used by the node)
- n8n documentation on Creating Custom Nodes