Evolution API icon

Evolution API

Complete WhatsApp automation with Evolution API
Join our community

Actions48

Overview

This node integrates with the Evolution API to automate WhatsApp messaging and media management. Specifically, the Download Media operation under the Media resource allows users to download media files from WhatsApp messages. This is useful in scenarios where you want to retrieve images, videos, audio, documents, or stickers sent or received via WhatsApp for further processing, storage, or analysis.

Practical examples include:

  • Automatically downloading media attachments from customer support chats for archival.
  • Fetching media content shared in group chats for moderation or record-keeping.
  • Integrating WhatsApp media downloads into broader workflows such as CRM updates or content management systems.

Properties

Name Meaning
Additional Fields Optional extra parameters:
• Delay (number): Delay in milliseconds before sending.
• Link Preview (boolean): Enable link preview in messages.
• Quoted Message ID (string): ID of message to quote/reply to.
• Mentions (string): Comma-separated list of numbers to mention.

Note: For the Download Media operation, the main required input properties (like message ID or media identifier) are implicitly handled by the node's internal logic or other parameters not explicitly listed here.

Output

The node outputs a JSON object containing the downloaded media data retrieved from the WhatsApp message. The structure typically includes metadata about the media and the media content itself encoded appropriately (e.g., as a URL or base64 string).

If the media is binary (such as images, videos, audio), the node will provide this data in the json output field, which can then be used downstream in the workflow for saving to disk, uploading elsewhere, or further processing.

Dependencies

  • Requires an active subscription and valid API keys for the Evolution API service.
  • Requires configuration of credentials within n8n for accessing the Evolution API and optionally the n8n Tools API for validation.
  • The node makes HTTP requests to the Evolution API endpoints; thus, internet connectivity and proper API endpoint access are necessary.

Troubleshooting

  • Invalid Subscription or API Key: If the node throws errors related to authentication (HTTP 401 or 403), verify that the API keys and subscription status for both Evolution API and n8n Tools API are correct and active.
  • Unknown Operation or Resource Errors: These occur if the selected operation or resource is not supported. Ensure the node parameters match the documented options.
  • Network Issues: Timeouts or connection errors may happen if the API endpoints are unreachable. Check network connectivity and firewall settings.
  • Missing Required Parameters: Some operations require specific inputs (e.g., phone number, message ID). Make sure all mandatory fields are filled correctly.
  • Rate Limits: Excessive requests might lead to throttling by the API provider. Implement delays or error handling to manage rate limits gracefully.

Links and References

Discussion