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
The node integrates with the Digitalsac API to manage scheduling operations, specifically allowing users to create new appointments ("Criar Agendamento"). This operation is useful for automating booking workflows such as client meetings, service appointments, or consultations. It supports specifying service details, selecting attendants, setting appointment date and time, and adding contact information. Optional features include sending customized messages, setting reminders, and closing related tickets automatically.
Practical examples:
- Automatically schedule a customer support call with a specific agent.
- Book a service appointment for a client with reminders sent before the event.
- Create an appointment and close the associated support ticket once scheduled.
Properties
| Name | Meaning |
|---|---|
| ID do Serviço | Numeric ID of the service to be scheduled. |
| Data | Date of the appointment in YYYY-MM-DD format. |
| Horário | Time of the appointment in HH:mm format (optional). |
| ID do Usuário | Numeric ID of the attendant/user assigned to the appointment. |
| Nome do Contato | Name of the client or contact person for the appointment. |
| Telefone do Contato | Phone number of the client/contact in international format (e.g., 5511999999999). |
| Observações | Optional notes or remarks about the appointment. |
| ID da Conexão WhatsApp | Optional numeric ID of the WhatsApp connection to use; if not provided, the first available is used. |
| Mensagem Personalizada | Optional custom message text related to the appointment. |
| Lembretes (minutos) | Comma-separated list of reminder times in minutes before the appointment (e.g., "60,240"). |
| Duração do Intervalo | Duration of the appointment interval in minutes. |
| Fechar Ticket | Boolean flag indicating whether to close the related ticket after creating the appointment. |
Output
The node outputs an array of JSON objects representing the response from the Digitalsac API after attempting to create the schedule. The JSON typically contains details about the created appointment or error information if the request failed.
Example output structure (simplified):
{
"id": 123,
"serviceId": 1,
"userId": 1,
"date": "2025-08-07",
"time": "09:00",
"contactName": "Client Name",
"contactPhone": "5511999999999",
"notes": "Optional notes",
"whatsappId": 0,
"message": "Custom message",
"reminders": [60, 240],
"intervalDuration": 30,
"closeTicket": false,
"status": "scheduled"
}
The node does not output binary data for this operation.
Dependencies
- Requires an API key credential for authenticating with the Digitalsac API.
- The base URL and token for the Digitalsac API must be configured in the node credentials.
- The node makes HTTP requests to Digitalsac endpoints to perform scheduling actions.
Troubleshooting
- Invalid JSON Format: If any JSON input fields are malformed (e.g., reminders or other JSON parameters), the node throws an error indicating invalid JSON format. Ensure all JSON inputs are correctly formatted.
- Missing Required Fields: Omitting required properties like service ID, date, or user ID may cause API errors or failed scheduling. Always provide mandatory fields.
- API Authentication Errors: If the API token is invalid or missing, requests will fail with authentication errors. Verify that the API key credential is correctly set up.
- Incorrect Phone Number Format: Contact phone numbers should follow the international format without spaces or special characters (e.g., 5511999999999). Invalid formats may cause failures.
- Empty or Incorrect WhatsApp Connection ID: If specifying a WhatsApp connection ID, ensure it exists and is valid; otherwise, the node defaults to the first available connection.
Links and References
- Digitalsac API Documentation (example link, replace with actual)
- n8n Documentation on Creating Custom Nodes
- General REST API usage in n8n: HTTP Request Node