Actions64
- Instance Actions
- Message Actions
- Group Actions
- Integration Actions
- Chat Actions
- Profile Actions
- Event Actions
Overview
The node "Evolution API" allows interaction with the Evolution API service. Specifically, for the Message resource and Send Text operation, it sends a text message to a specified recipient number via an instance of the Evolution API messaging system.
This node is useful in scenarios where automated text messaging is required, such as sending notifications, alerts, or customer communications programmatically. For example, you can use it to send appointment reminders, marketing messages, or support updates directly from your workflow.
Properties
| Name | Meaning |
|---|---|
| Instance Name | The name of the instance that will send the message. |
| Recipient Number | The recipient's RemoteJid (phone number or identifier) to which the text message will be sent. |
| Message | The text content of the message to be sent. |
| Options | Additional optional settings for the message: |
| - Delay | Milliseconds to wait before sending the message (default 1200 ms). |
| - Reply Message | ID of a message to reply to (quoted message). |
| - Mentions | Settings for mentioning participants: either mention everyone in a group or specify numbers to mention. |
| - Link Preview | Enable or disable link preview in the message (boolean, default true). |
Output
The node outputs a JSON array containing the response from the Evolution API after attempting to send the message. This typically includes details about the message status, confirmation, or any error information returned by the API.
No binary data output is indicated.
Dependencies
- Requires an active connection to the Evolution API service.
- Requires configuration of an API authentication credential (an API key or token) within n8n credentials.
- The base URL for requests is
https://doc.evolution-api.com/api-reference.
Troubleshooting
- Operation not supported error: If the selected resource-operation combination is not implemented, the node throws an error indicating the function is unsupported. Ensure you select valid resource and operation pairs.
- Missing required parameters: The node requires at least the recipient number and message text. Omitting these will cause errors.
- API authentication issues: Make sure the API key/token credential is correctly configured and has sufficient permissions.
- Delay setting: Setting an excessively high delay may cause unexpected workflow timing; keep delays reasonable.
- Mentioning users: When using mentions, ensure the phone numbers are correctly formatted and separated by commas if multiple.
Links and References
- Evolution API Documentation (base URL used by the node)
- n8n documentation on Creating Custom Nodes