Actions64
- Instancia Actions
- Mensagem Actions
- Grupo Actions
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
Overview
The node "Evolution API Direct" allows users to interact with the Evolution API by sending requests directly using a specified server URL and API key. Specifically, for the resource Mensagem and operation Enviar Imagem, this node sends an image message to a recipient via the Evolution API. This is useful in scenarios where automated image messaging is required, such as sending promotional images, notifications, or alerts through a messaging platform integrated with Evolution API.
Practical examples include:
- Sending product images to customers automatically after an order confirmation.
- Broadcasting event flyers or invitations to a group of recipients.
- Replying with images in customer support chatbots.
Properties
| Name | Meaning |
|---|---|
| Server URL | The full URL of your Evolution API endpoint (e.g., https://api.exemplo.com). |
| API Key | The API key credential used to authenticate requests to the Evolution API instance. |
| Nome Da Instancia | The name of the instance that will send the message. |
| Número Do Destinatário | The recipient's phone number or identifier to whom the image will be sent. |
| Imagem | The image to send, provided either as a URL or base64 encoded string. |
| Caption | Optional text caption to accompany the image message. |
| Opções (Options) | Additional optional settings: |
| - Delay | Time in milliseconds to wait before sending the message (default 1200 ms). |
| - Responder Mensagem | Option to reply to a specific message by providing its message ID. |
| - Menções | Settings to mention participants in a group message: |
| -- Mencionar Todos | Boolean to mention all participants in the group. |
| -- Números Para Mencionar | Comma-separated list of numbers to mention individually if not mentioning everyone. |
Output
The node outputs a JSON array containing the response from the Evolution API after attempting to send the image message. The structure typically includes details about the message status, IDs, timestamps, or error information if the request failed.
If the API supports binary data responses (not explicitly shown here), the node would handle it accordingly, but based on the provided code and properties, the output focuses on JSON metadata about the sent message.
Dependencies
- Requires access to the Evolution API endpoint specified by the user.
- Needs a valid API key credential for authentication.
- The node expects the user to provide correct instance names and recipient identifiers compatible with the Evolution API.
- No additional external libraries beyond n8n core dependencies are indicated.
Troubleshooting
Common Issues:
- Incorrect or missing Server URL or API Key will cause authentication failures.
- Invalid recipient number format may result in message delivery errors.
- Providing an invalid image URL or malformed base64 string can cause the API to reject the media.
- Delay values too low might cause rate limiting or unexpected behavior.
Error Messages:
"Operação não suportada."indicates the requested operation is not implemented or recognized by the node.- API errors returned from the Evolution API will be passed through; check the API documentation for error codes.
Resolutions:
- Verify all required fields are correctly filled.
- Ensure the API key has sufficient permissions.
- Validate image URLs or base64 strings before sending.
- Use appropriate delay values to avoid flooding the API.
Links and References
- Evolution API Documentation (as referenced in the node defaults)
- n8n Documentation on Creating Custom Nodes