Actions64
- Instancia Actions
- Mensagem Actions
- Grupo Actions
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
Overview
This node integrates with the Evolution API to send documents as messages. Specifically, the "Enviar Documento" operation under the "Mensagem" resource allows users to send a document file (such as PDF or other supported formats) to a specified recipient via an instance of the Evolution messaging service.
Common scenarios include:
- Automating the sending of invoices, contracts, or reports as attachments.
- Distributing official documents to clients or team members.
- Sending any file-based information alongside optional text captions and mentions in group chats.
For example, a user can configure this node to send a PDF invoice to a customer’s phone number with a personalized message and optionally mention specific participants in a group chat.
Properties
| Name | Meaning |
|---|---|
| Nome Da Instância | The name of the Evolution API instance that will send the document. |
| Número Do Destinatário | The recipient's phone number or identifier where the document will be sent. |
| Documento | The document to send, provided as a URL or base64 encoded string. |
| Mensagem | Optional text message to accompany the document. |
| Nome Do Arquivo | The filename to assign to the sent document (default is "document.pdf"). |
| Opções | Additional options for sending the message: |
| - 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 in the message: |
| -- 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 document message. This typically includes confirmation details such as message IDs, status, timestamps, or error information if the send failed.
No binary data output is indicated; the output focuses on JSON metadata about the sent message.
Dependencies
- Requires an active Evolution API account with valid credentials configured in n8n.
- The node depends on network access to the Evolution API endpoint (
https://doc.evolution-api.com/api-reference). - Proper API authentication tokens or keys must be set up in n8n credentials for the Evolution API.
Troubleshooting
Common issues:
- Invalid or missing instance name may cause failure to identify the sending context.
- Incorrect recipient number format can lead to delivery errors.
- Providing an invalid document URL or malformed base64 string will prevent the document from being sent.
- Mentioning users incorrectly (wrong phone numbers or formatting) might cause mention failures.
- Delay values too low or too high could affect timing unexpectedly.
Error messages:
"Operação não suportada."indicates the selected operation is not implemented or recognized.- API errors returned from Evolution API will be surfaced in the node output; check for authentication errors or quota limits.
Resolutions:
- Verify all required fields are correctly filled.
- Ensure the document source is accessible and properly formatted.
- Confirm that the API credentials are valid and have necessary permissions.
- Use the delay option to avoid rate limiting or timing conflicts.
Links and References
- Evolution API Documentation (official API reference)
- n8n documentation on creating custom nodes for further customization guidance