Evolution API icon

Evolution API

Complete WhatsApp automation with Evolution API
Join our community

Actions48

Overview

This node enables sending media messages via WhatsApp using the Evolution API. It supports sending various types of media such as images, videos, audio files, documents, and stickers to a specified phone number. The node is useful for automating multimedia communication workflows, such as sending promotional content, customer support attachments, or informational media files directly through WhatsApp.

For example, you can use this node to send a product brochure PDF to a customer or share a video tutorial link with your audience automatically.

Properties

Name Meaning
Phone Number The recipient's phone number including country code (without the "+" sign).
Media URL The URL or base64 encoded data of the media file to be sent.
Caption Optional text caption to accompany the media message (supported for image, video, document).
Additional Fields A collection of optional parameters:
- Delay: Time in milliseconds to wait before sending.
- Link Preview: Enable or disable link preview in messages.
- Quoted Message ID: ID of a message to quote or reply to.
- Mentions: Comma-separated list of phone numbers to mention in the message.

Output

The node outputs a JSON object containing the response from the Evolution API after attempting to send the media message. This typically includes details about the message status, IDs, or any errors returned by the API.

If the operation fails and "Continue On Fail" is enabled, the output will contain an error message describing the failure.

No binary data output is produced by this node.

Dependencies

  • Requires an active Evolution API credential with a valid API key, base URL, and instance name configured in n8n.
  • Optionally uses an additional API validation service requiring its own API key and URL.
  • The node sends HTTP requests to the Evolution API endpoints to perform actions.
  • Proper network connectivity to the Evolution API service is necessary.

Troubleshooting

  • Invalid Credentials: If the API key or instance name is incorrect, the node will fail authentication. Verify credentials in n8n settings.
  • API Validation Failure: Errors like "Invalid subscription or API key" indicate issues with the secondary validation API. Check that the validation API key is correct and the subscription is active.
  • Unknown Operation or Resource: If an unsupported operation or resource is selected, the node throws an error. Ensure the operation matches the supported options.
  • Media URL Issues: Invalid or inaccessible media URLs will cause the send request to fail. Confirm the media URL is publicly accessible or correctly formatted base64 data.
  • Delay Misconfiguration: Setting a very high delay may cause unexpected workflow timing; ensure delay values are reasonable.
  • Message Quoting and Mentions: Incorrect message IDs or mention formats may result in errors or ignored mentions.

Links and References

Discussion