Actions64
- Instance Actions
- Message Actions
- Group Actions
- Integration Actions
- Chat Actions
- Profile Actions
- Event Actions
Overview
The node named "Evolution API" provides an interface to interact with the Evolution API service. Specifically, for the resource Chat and operation Get Media in Base64, it retrieves media content from a chat message by its ID and returns the media encoded as a Base64 string. This is useful when you want to programmatically access media files (images, videos, audio) sent or received in chat messages and process or store them in workflows without dealing with raw file downloads.
Common scenarios include:
- Extracting images or videos from chat conversations for archival or analysis.
- Converting video formats on the fly (e.g., converting videos to MP4).
- Integrating chat media into other systems that require Base64 encoded data.
Example: You have a chat system integrated via Evolution API and want to fetch a video sent in a message, convert it to MP4 format, and then upload it to a cloud storage service.
Properties
| Name | Meaning |
|---|---|
| Instance Name | The name of the Evolution API instance to connect to. |
| Message ID | The unique identifier of the chat message containing the media to retrieve. |
| Convert to MP4 | Boolean flag indicating whether to convert the retrieved video media to MP4 format. |
Output
The node outputs a JSON array where each item contains the media data encoded as a Base64 string under the json property. This allows subsequent nodes to easily consume the media content for further processing or storage.
If the media is a video and the "Convert to MP4" option is enabled, the output will be the converted MP4 video encoded in Base64.
No binary data output is indicated; all media is returned as Base64 within JSON.
Dependencies
- Requires an active connection to the Evolution API service.
- Needs an API authentication credential configured in n8n to authorize requests.
- The node depends on the Evolution API's availability and correct configuration of the instance name.
Troubleshooting
- Operation not supported error: If the specified resource-operation combination is invalid or not implemented, the node throws an error stating the operation is unsupported. Verify the resource and operation names are correct.
- Invalid or missing credentials: Ensure the API key or authentication token for the Evolution API is correctly set up in n8n.
- Message ID not found: If the provided message ID does not exist or does not contain media, the API may return an error or empty result.
- Conversion failures: If "Convert to MP4" is enabled but the media cannot be converted (unsupported format or API limitation), the node might fail or return an error. Check media compatibility and API documentation.
Links and References
- Evolution API Documentation (base URL referenced in code)
- n8n Documentation on Creating Custom Nodes