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, providing a variety of operations related to customer service automation and scheduling. Specifically, the "Listar Usuários Disponíveis" (List Available Users) operation retrieves a list of users available for a given service on a specified date and optionally at a specific time.
Common scenarios where this node is beneficial include:
- Scheduling systems where you need to find which users (e.g., agents or service providers) are available to handle appointments or tasks.
- Automating workflows that require dynamic allocation of resources based on availability.
- Integrations with CRM or helpdesk platforms to coordinate user availability.
Practical example:
- A business wants to show customers which support agents are available on a certain day before booking an appointment. Using this node's "Listar Usuários Disponíveis" operation, it can fetch and display available users filtered by service ID and date/time.
Properties
| Name | Meaning |
|---|---|
| ID do Serviço | Numeric ID of the service to filter available users. |
| Data | Date in the format YYYY-MM-DD to check user availability. |
| Horário | Optional time in the format HH:mm to further filter available users at a specific time. |
Output
The output is a JSON object containing the response from the Digitalsac API endpoint /typebot/listar_usuarios_disponiveis. This typically includes a list of users available for the specified service and date/time.
The exact structure depends on the API but generally will be an array or object listing user details such as IDs, names, and availability status.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for the Digitalsac API.
- The node uses the base URL and token from these credentials to authenticate requests.
- The node makes HTTP GET requests to the Digitalsac API endpoints.
- Proper configuration of the Digitalsac API credentials in n8n is necessary.
Troubleshooting
- Invalid or missing credentials: Ensure the API key/token is correctly configured in n8n credentials; otherwise, authentication errors will occur.
- Invalid date or time format: The
scheduleDatemust be inYYYY-MM-DDformat andscheduleTimeinHH:mmif provided. Incorrect formats may cause API errors or empty results. - Empty or no results: If no users are returned, verify that the service ID and date/time parameters correspond to actual available users in the Digitalsac system.
- Network or API errors: Check network connectivity and API status if requests fail or return error messages.
- Parameter validation: The node does not perform deep validation beyond basic formatting; ensure all required fields are filled.
Links and References
- Digitalsac API Documentation (Assumed official API docs, replace with actual if available)
- n8n documentation on HTTP Request Node for understanding how API calls work within n8n.
- General info on ISO 8601 date and time formats for correct input formatting.