Actions64
- Instancia Actions
- Mensagem Actions
- Grupo Actions
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
Overview
This node, named "Evolution API Direct," allows users to interact with the Evolution API by specifying a direct server URL and an API key. It supports various resources and operations; here, the focus is on the Chat resource with the operation Obter Mídia Em Base64 (Get Media in Base64). This operation retrieves media content from a chat message by its ID and returns it encoded in Base64 format. Optionally, if the media is a video, it can be converted to MP4 format.
Typical use cases include:
- Downloading media attachments from chat messages for further processing or storage.
- Integrating chat media retrieval into automated workflows, such as archiving images or videos.
- Converting video formats automatically when retrieving media to ensure compatibility.
Properties
| Name | Meaning |
|---|---|
| Server URL | The full URL of your Evolution API server endpoint (e.g., https://api.exemplo.com). |
| API Key | The API key credential required to authenticate requests to the Evolution API instance. |
| Nome Da Instância | The name of the specific Evolution API instance you want to target. |
| ID Da Mensagem | The unique identifier of the chat message that contains the media to retrieve. |
| Converter Para MP4 | Boolean flag indicating whether to convert the retrieved video media to MP4 format (true or false). |
Output
The node outputs a JSON array where each item corresponds to the result of the media retrieval operation. The main output field is:
json: Contains the media data encoded as a Base64 string. If the media is a video and conversion is requested, this will be the Base64 representation of the MP4-converted video.
If the media includes binary data, it would typically be represented in Base64 within the JSON output, allowing easy integration with other nodes or systems expecting encoded media content.
Dependencies
- Requires access to the Evolution API server specified by the user via the Server URL.
- Requires a valid API key credential for authentication.
- The node depends on the Evolution API's availability and correct configuration of the instance name and message ID.
- No additional external libraries are indicated beyond standard n8n workflow dependencies.
Troubleshooting
Common Issues:
- Incorrect Server URL or API Key will cause authentication failures.
- Providing an invalid or non-existent message ID will result in errors or empty responses.
- If the media is not a video but the "Convert to MP4" option is enabled, the conversion may fail or be ignored.
Error Messages:
"Operação não suportada."indicates that the selected operation is not implemented for the chosen resource.- Network or authentication errors usually stem from incorrect API credentials or server unavailability.
Resolutions:
- Verify the Server URL and API Key are correct and have necessary permissions.
- Confirm the message ID exists and contains media.
- Disable video conversion if unsure about media type or if conversion fails.
Links and References
- Evolution API Documentation (as referenced in the code defaults)
- General n8n documentation on Creating Custom Nodes