Actions64
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
- Instancia Actions
- Mensagem Actions
- Grupo Actions
Overview
This node, named "Evolution API," allows users to send a video message through a messaging API by specifying the instance name, recipient number, and video content. It is useful for automating video message delivery in workflows such as customer support, marketing campaigns, or notifications where sending multimedia content is required.
For example, you can use this node to automatically send a promotional video to a list of customers or to share instructional videos with users after they complete a certain action.
Properties
| Name | Meaning |
|---|---|
| Nome Da Instância | The name of the instance that will send the video. |
| Número Do Destinatário | The phone number of the recipient who will receive the video message. |
| Video | The video content to send, provided as a URL or base64 string. |
| Caption | Optional text caption to be sent along with the video. |
| Opções | Additional options for sending the message: |
| - Delay | Number of milliseconds to wait before sending the message (default 1200 ms). |
| - Responder Mensagem | ID of a message to which this video message will reply. |
| - Menções | Settings for mentioning participants in a group: |
| -- 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 API after attempting to send the video message. This typically includes information about the success or failure of the operation, message IDs, timestamps, or other metadata returned by the messaging service.
If the node supports binary data output (not explicitly shown here), it would represent the media content or related attachments, but based on the provided code and properties, the output focuses on JSON responses.
Dependencies
- Requires an API key credential for authenticating with the Evolution API.
- The node expects the user to provide valid instance names and recipient phone numbers.
- Network access to the Evolution API endpoint is necessary.
- No additional external libraries beyond those bundled with n8n are indicated.
Troubleshooting
Common Issues:
- Invalid or missing instance name or recipient number will cause the operation to fail.
- Incorrect video URL or improperly formatted base64 string may result in upload errors.
- Mentioning users incorrectly (wrong phone number format) might cause the message to send without mentions.
- Delay values that are too low or too high could affect timing unexpectedly.
Error Messages:
"Operação não suportada."indicates that the selected operation is not implemented for the chosen resource.- API authentication errors if the API key is invalid or missing.
- Network or timeout errors if the Evolution API is unreachable.
Resolutions:
- Verify all required fields are correctly filled.
- Ensure the video source is accessible and properly formatted.
- Check API credentials and network connectivity.
- Use correct phone number formats and mention settings.
Links and References
- Evolution API official documentation (not provided here; consult your API provider)
- n8n documentation on creating custom nodes and handling multimedia messages
- General best practices for sending media via messaging APIs