Evolution API icon

Evolution API

Interact with Evolution API

Overview

The "Enviar Texto" operation of the "Mensagem" resource in this node allows sending text messages to specified phone numbers via the Evolution API. It is useful for automating communication workflows such as notifications, alerts, or customer engagement through messaging platforms that support phone number-based messaging.

Typical use cases include:

  • Sending automated reminders or confirmations to customers.
  • Broadcasting updates or announcements to a list of recipients.
  • Replying to user inquiries programmatically.

Properties

Name Meaning
Nome Da Instancia The name of the instance that will send the message.
To Recipient phone number (digits only, optional leading +). Supports expressions for dynamic input.
Message Text The content of the text message to be sent. Supports expressions for dynamic content generation.
Message Type Type of message to send. Options: Text (default), Image, Audio, Video, Document (latter four are future use).
Opções Additional options for the message:
- Delay Delay in milliseconds before sending the message (default 1200 ms).
- Responder Mensagem Option to reply to a specific message by providing its ID.
- Menções Settings for mentions within the message:
- Mencionar Todos Boolean to mention all participants in a group.
- Números Para Mencionar Comma-separated list of phone numbers to mention individually (if not mentioning all).
- Preview De Link Enable or disable link preview in the message (default enabled).

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, IDs, timestamps, or error information if the send failed.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating with the Evolution API.
  • The node uses the base URL https://doc.evolution-api.com/api-reference for API requests.
  • Proper configuration of the API credential in n8n is necessary for successful execution.

Troubleshooting

  • Common Issues:

    • Invalid or missing recipient phone number format may cause errors.
    • Missing or incorrect API credentials will prevent message sending.
    • Network connectivity issues can lead to request failures.
    • Using unsupported message types currently marked as "future use" may not work.
  • Error Messages:

    • "Operação não suportada." indicates the requested operation is not implemented or recognized.
    • API errors returned from the Evolution API will be passed through; check the message and description fields for details.
  • Resolutions:

    • Verify phone number formatting (digits only, optional leading +).
    • Ensure API credentials are correctly set up and valid.
    • Confirm network access to the Evolution API endpoint.
    • Use only supported message types ("text") until others are implemented.

Links and References

Discussion