Actions64
- Instancia Actions
- Mensagem Actions
- Grupo Actions
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
Overview
The Obter Mídia Em Base64 operation of the Chat resource in this custom n8n node is designed to retrieve media content (such as images, audio, or video) from a chat message by its ID and return it encoded in Base64 format. Optionally, if the media is a video, it can be converted to MP4 format before encoding. This is useful for automating workflows that need to process, store, or forward media files received via chat platforms integrated with Evolution API.
Practical examples:
- Automatically saving incoming WhatsApp voice notes or images to a cloud storage service.
- Forwarding received videos (converted to MP4) to another system or user.
- Processing media attachments for further analysis or reporting.
Properties
| Display Name | Type | Meaning |
|---|---|---|
| Nome Da Instância | String | The name of the instance to connect to. Required to identify which chat instance to use. |
| ID Da Mensagem | String | The unique identifier of the message containing the media you want to retrieve. |
| Converter Para MP4 | Boolean | If enabled, converts the retrieved video to MP4 format before returning as Base64. |
Output
The node outputs a JSON object containing the requested media in Base64 format. The exact structure may vary depending on the API response, but typically includes:
{
"media": "<base64-encoded-string>",
"mimeType": "string",
"fileName": "string"
}
media: The media file encoded as a Base64 string.mimeType: The MIME type of the media (e.g., image/jpeg, video/mp4).fileName: The original or generated filename for the media.
If binary data output is supported, it would represent the raw media file, but in this operation, the focus is on Base64-encoded output.
Dependencies
- External Service: Requires access to the Evolution API.
- Credentials: You must configure valid Evolution API credentials in n8n under the name
evolutionApi. - n8n Configuration: No additional environment variables are required beyond standard credential setup.
Troubleshooting
Common issues:
- Invalid Instance Name: If the provided instance name does not exist or is incorrect, the node will fail to retrieve the media.
- Incorrect Message ID: Supplying an invalid or non-existent message ID will result in errors or empty responses.
- Unsupported Media Type: Attempting to convert non-video media to MP4 may cause errors.
- Missing Credentials: If the Evolution API credentials are not set up correctly, authentication errors will occur.
Error messages:
"Operação não suportada."- Cause: The selected operation is not implemented for the chosen resource.
- Resolution: Double-check that you have selected the correct resource and operation combination.