Evolution API

Interagir com a Evolution API v2
Join our community

Actions53

Overview

This node integrates with the Evolution API v2 to perform various operations related to messaging, instances, groups, chats, events, and integrations. Specifically, for the Mensagem (Message) resource and the Enviar Documento (Send Document) operation, it allows sending a document file to a specified recipient's number via an instance of the Evolution platform.

Typical use cases include automating document delivery through WhatsApp or similar messaging services managed by the Evolution API. For example, businesses can automatically send invoices, contracts, or brochures as documents to customers directly from their workflows.

Properties

Name Meaning
Instance Name The name of the Evolution API instance to use for sending the document.
Number The recipient's phone number to which the document will be sent.
Document URL The URL where the document file is hosted and accessible for sending.
Document Name The name of the document file as it should appear to the recipient.

Output

The node outputs a JSON object containing the response from the Evolution API after attempting to send the document. The output includes:

  • success: A boolean indicating if the operation was successful.
  • timestamp: The ISO string timestamp when the operation completed.
  • Additional fields returned by the API, which may include message IDs, status, or error details depending on the API response.

No binary data is output by this node; all responses are in JSON format.

Dependencies

  • Requires an active Evolution API v2 credential configured in n8n for authentication.
  • The node makes HTTP requests to the Evolution API endpoints.
  • The document must be accessible via a public URL for the API to fetch and send it.

Troubleshooting

  • Common Issues:

    • Invalid or unreachable Document URL: Ensure the URL is publicly accessible and points directly to the document file.
    • Incorrect Instance Name: Verify that the instance name matches an existing and connected Evolution API instance.
    • Invalid recipient Number format: Confirm the phone number is correctly formatted as expected by the Evolution API.
    • Authentication errors: Check that the API key or credentials are valid and have necessary permissions.

  • Error Messages:

    • Network or timeout errors when calling the API usually indicate connectivity issues or incorrect endpoint URLs.
    • API response errors may include messages about invalid parameters or unauthorized access; review the input properties and credentials.
    • If the node returns an error object, enabling "Continue On Fail" can help process subsequent items without stopping the workflow.

Links and References

Discussion