Actions64
- Instancia Actions
- Mensagem Actions
- Grupo Actions
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
Overview
The node "Evolution API" allows interaction with the Evolution API to send various types of messages. Specifically, for the resource Mensagem and operation Enviar Video, it enables sending a video message to a specified recipient via an instance of the Evolution API service.
This node is useful in scenarios where automated or programmatic sending of video content is required, such as:
- Customer support systems sending tutorial or product videos.
- Marketing campaigns delivering promotional videos.
- Notification systems that include video attachments.
For example, you can configure the node to send a video URL or base64 encoded video to a WhatsApp number with an optional caption and mentions.
Properties
| Name | Meaning |
|---|---|
| Nome Da Instância | The name of the Evolution API instance that will send the video. |
| Número Do Destinatário | The recipient's phone number in international format (e.g., 5511999999999). |
| Video | The video content to send, provided as a URL or base64 string. |
| Caption | Optional text message to accompany the video. |
| Opções | Additional options for sending the message: |
| - Delay | Time in milliseconds to wait before sending the message (default 1200 ms). |
| - Responder Mensagem | ID of a message to reply to (quoted message). |
| - Menções | Settings for mentioning users in group chats: |
| -- Mencionar Todos | Boolean to mention all participants in the group. |
| -- Números Para Mencionar | Comma-separated list of phone numbers to mention individually (if not mentioning all). |
Output
The node outputs a JSON array containing the response from the Evolution API after attempting to send the video message. The exact structure depends on the API response but typically includes confirmation details such as message ID, status, timestamps, or error information if the send failed.
If the node supports binary data output (not explicitly shown here), it would represent media content or related files, but for this operation, the focus is on JSON metadata about the sent video message.
Dependencies
- Requires an active Evolution API account with valid API credentials configured in n8n.
- The node expects the Evolution API base URL and authentication headers to be set up correctly.
- Network access to the Evolution API endpoint is necessary.
- The video must be accessible either as a URL or provided as base64 encoded data.
Troubleshooting
Common Issues:
- Invalid or missing instance name or recipient number will cause failures.
- Incorrect video URL or malformed base64 data may result in upload errors.
- API authentication errors if credentials are misconfigured.
- Delay option too low might cause rate limiting or message ordering issues.
Error Messages:
"Operação não suportada."indicates the requested operation is not implemented or recognized.- API errors returned by Evolution API will usually contain HTTP status codes and descriptive messages; check credentials and input formats.
Resolutions:
- Verify all required fields are filled correctly.
- Ensure the video source is reachable and properly formatted.
- Confirm API credentials and permissions.
- Adjust delay settings if encountering rate limits.
Links and References
- Evolution API Documentation (official API reference)
- n8n documentation on Creating Custom Nodes