Evolution API Direct icon

Evolution API Direct

Interact with Evolution API using direct URL and API Key

Actions64

Overview

The node "Evolution API Direct" allows sending a video message through the Evolution API by specifying the target instance, recipient number, and video content. It is useful for automating multimedia messaging workflows, such as sending promotional videos, customer support clips, or notifications with video attachments directly to WhatsApp or similar platforms supported by the Evolution API.

Typical use cases include:

  • Sending marketing videos to customers.
  • Delivering instructional or informational videos automatically.
  • Responding to user queries with video content in chatbots or automated systems.

Properties

Name Meaning
Server URL The full URL of your Evolution API endpoint (e.g., https://api.exemplo.com).
API Key The API key credential required to authenticate requests to the Evolution API.
Nome Da Instância The name of the instance that will send the video message.
Número Do Destinatário The recipient's phone number in international format to which the video will be sent.
Video The video content to send, provided as a URL or base64 encoded string.
Caption Optional text caption to accompany the video message.
Opções (Options) Additional message options:
- Delay Time in milliseconds to wait before sending the message (default 1200 ms).
- Responder Mensagem Optionally reply to a specific message by providing its message ID.
- Menções Mention settings:
- Mencionar Todos Boolean to mention all participants in a group.
- Números Para Mencionar Comma-separated list of phone numbers to mention individually (if not mentioning everyone).

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, message IDs, timestamps, or error details if the operation failed.

No binary data output is produced by this node; all responses are JSON-formatted metadata about the sent message.

Dependencies

  • Requires access to the Evolution API via a valid server URL and an API key credential.
  • The node expects the user to provide correct instance names and recipient phone numbers formatted according to the API requirements.
  • No additional external libraries beyond those bundled with n8n are needed.

Troubleshooting

  • Common issues:

    • Invalid or missing API key or server URL will cause authentication failures.
    • Incorrect instance name or recipient number format may result in message delivery errors.
    • Providing an invalid video URL or malformed base64 string can cause media upload failures.
    • Delay values too low might cause rate limiting or message queuing issues on the API side.

  • Error messages:

    • "Operação não suportada." indicates the requested operation is not implemented for the selected resource.
    • API errors returned from the Evolution API will be included in the node output; check these for details like invalid credentials, quota exceeded, or unsupported media types.

  • Resolutions:

    • Verify API key and server URL correctness.
    • Ensure instance and recipient identifiers follow expected formats.
    • Validate video URLs or base64 strings before sending.
    • Adjust delay settings if encountering rate limits.

Links and References

Discussion