Evolution API icon

Evolution API

Interact with Evolution API

Actions64

Overview

The node "Evolution API" allows interaction with the Evolution API service. Specifically, for the Message resource and Send Video operation, it sends a video message to a specified recipient number via an instance of the Evolution API messaging system.

This node is useful in scenarios where automated sending of video content is required, such as:

  • Customer support systems sending tutorial or troubleshooting videos.
  • Marketing campaigns delivering promotional videos directly to users.
  • Notification systems that include video updates or alerts.

For example, a business could use this node to send a welcome video to new customers automatically after signup.

Properties

Name Meaning
Instance Name The name of the Evolution API instance that will send the video message.
Recipient Number The phone number of the message recipient in international format (e.g., including country code).
Video The video content to send, provided as a URL or base64 encoded string.
Caption Optional text caption to accompany the video message.
Options Additional optional settings:
- Delay Time in milliseconds to wait before sending the message (default 1200 ms).
- Reply Message Optionally specify a message ID to which this video message will be sent as a reply.
- Mentions Settings to mention participants in group chats:
- Mention Everyone Boolean flag to mention all participants in the group.
- Numbers To Mention Comma-separated list of specific numbers to mention in the message.

Output

The node outputs a JSON array containing the response from the Evolution API after attempting to send the video message. This typically includes status information about the message delivery.

If the node supports binary data output (not explicitly shown here), it would represent media content or attachments related to the message.

Dependencies

  • Requires an active Evolution API account with valid API credentials configured in n8n.
  • The node depends on network access to the Evolution API endpoint (https://doc.evolution-api.com/api-reference).
  • Proper configuration of the instance name and authentication token is necessary for successful message sending.

Troubleshooting

  • Common Issues:

    • Invalid or missing instance name or API credentials will cause authentication failures.
    • Incorrect recipient number format may result in message delivery errors.
    • Sending large video files or unsupported formats might lead to API rejections.
    • Network connectivity issues can prevent communication with the Evolution API.

  • Error Messages:

    • "Operation not supported." — indicates the requested operation is not implemented; verify the resource and operation names.
    • Authentication errors suggest checking API key validity and permissions.
    • Timeout or connection errors require verifying internet access and API endpoint availability.

Links and References

Discussion