Actions23
- Validar WhatsApp
- Validar CPF
- Validar Data
- Transferir para Fila
- Transferir para Atendente
- Fechar Ticket
- Enviar Mensagem
- Enviar Botões
- Enviar Lista
- Enviar Mídia com Caption
- Enviar Base64
- Vincular Tag
- Criar Tag
- Listar Kanbans
- Vincular Kanban
- Vincular Carteira
- Listar Serviços
- Listar Usuários Disponíveis
- Listar Horários Disponíveis
- Listar Agendamentos
- Criar Agendamento
- Cancelar Agendamento
- Gerar Link do Calendário (.ics)
Overview
This node integrates with the Digitalsac API to perform various operations related to messaging, validation, ticket management, scheduling, and more. Specifically, the "Enviar Base64" operation allows sending a media file encoded in Base64 format via WhatsApp through the Digitalsac platform.
Common scenarios for using this node include:
- Sending images, documents, or other media files directly from n8n workflows to WhatsApp contacts without needing to upload files separately.
- Automating customer support interactions by sending media content dynamically.
- Integrating with CRM or ticketing systems to send attachments as part of communication flows.
Example use case:
- A workflow that generates a PDF invoice, encodes it in Base64, and sends it automatically to a customer's WhatsApp number with an optional caption.
Properties
| Name | Meaning |
|---|---|
| Parâmetro | UUID of the connection (required for this operation). |
| Chave Externa | Optional unique identifier for the message (default: "Digitalsac123"). |
| Caption (Opcional) | Optional caption text to accompany the Base64 media file. |
| Número de Telefone | Phone number in international format (DDI+DDD+Number), e.g., 5511999999999. |
| Arquivo Base64 | The media file content encoded as a Base64 string (required). |
| Tipo MIME | MIME type of the file, e.g., image/png, application/pdf (required). |
| Nome do Arquivo | File name including extension, e.g., arquivo.png (required). |
Output
The node outputs a JSON object containing the response from the Digitalsac API after attempting to send the Base64 media message. The structure typically includes success confirmation or error details.
If an error occurs during the request, the output JSON will contain an error field describing the issue.
No binary data is output by this operation.
Dependencies
- Requires an API key credential for authenticating with the Digitalsac API.
- The node expects the base URL and token for the Digitalsac API to be configured in the credentials.
- The phone number must be formatted correctly (international format without spaces or symbols).
- The Base64 media string must be valid and properly encoded.
Troubleshooting
- Missing UUID ("Parâmetro"): The operation requires the UUID of the connection. If omitted or empty, the node throws an error instructing to fill this field.
- Invalid or missing Base64 file: If the Base64 string is empty or invalid, an error is thrown indicating the Base64 file is mandatory.
- Missing MIME type or file name: Both are required; if missing, errors specify these fields must be provided.
- API request failures: Errors returned by the Digitalsac API are passed through in the output under the
errorkey. Check the API token validity and network connectivity. - Incorrect phone number format: Ensure the phone number is in the correct DDI+DDD+Number format without extra characters.
Links and References
- Digitalsac API Documentation (example placeholder, replace with actual link if available)
- WhatsApp Business API Media Messages
- Base64 Encoding Reference