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 users to interact with the Evolution API by sending documents as messages. Specifically, the "Enviar Documento" (Send Document) operation under the "Mensagem" (Message) resource enables sending a document file to a specified recipient via the Evolution API. This is useful in scenarios where automated workflows need to deliver files such as PDFs or other documents directly to users or groups through the messaging platform integrated with Evolution API.

Practical examples include:

  • Sending invoices or contracts automatically after a form submission.
  • Delivering reports or certificates to clients or team members.
  • Sharing manuals or guides as part of customer support automation.

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 for authenticating requests to the Evolution API instance or global scope.
Nome Da Instância The name of the Evolution API instance that will send the document.
Número Do Destinatário The recipient's number (remote JID) to whom the document will be sent.
Documento The document content, provided either as a URL or base64 string representing the file to send.
Mensagem Optional text message (caption) to accompany the document.
Nome Do Arquivo The filename to assign to the sent document (default is "document.pdf").
Opções Additional options including:
- Delay Time in milliseconds to wait before sending the message (default 1200 ms).
- Responder Mensagem Option to reply to a specific message by providing its ID.
- Menções Settings to mention participants: either mention everyone or specify individual numbers separated by commas.

Output

The node outputs a JSON array containing the response from the Evolution API after attempting to send the document message. The exact structure depends on the API response but typically includes confirmation details such as message IDs, status, timestamps, or error information if the send failed.

If the API supports binary data responses, this node primarily deals with sending binary content (documents) rather than outputting binary data itself.

Dependencies

  • Requires access to the Evolution API endpoint specified by the user.
  • Needs a valid API key credential for authentication.
  • Proper configuration of the instance name and recipient number is mandatory.
  • Network connectivity to the specified server URL.

Troubleshooting

  • Common Issues:

    • Invalid or missing API key leading to authentication errors.
    • Incorrect server URL causing connection failures.
    • Wrong recipient number format resulting in delivery failure.
    • Document URL or base64 data improperly formatted or inaccessible.

  • Error Messages:

    • "Operation not supported": Occurs if an unsupported operation or resource is selected.
    • API errors returned from the Evolution API (e.g., 401 Unauthorized, 404 Not Found) should be checked against credentials and endpoint correctness.

  • Resolutions:

    • Verify API key validity and permissions.
    • Confirm the server URL is correct and reachable.
    • Ensure recipient numbers follow the expected format.
    • Validate document input (URL accessible or base64 correctly encoded).
    • Use delay option if rate limiting or timing issues occur.

Links and References

Discussion