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 customer service and ticket management operations. Specifically, the "Transferir para Atendente" (Transfer to Agent) operation allows transferring a support ticket to a specific agent (attendant). This is useful in scenarios where a ticket needs to be reassigned to another team member for specialized handling or workload balancing.
Practical examples:
- Automatically transfer a customer support ticket to a senior agent based on ticket priority.
- Reassign tickets to available agents during shift changes.
- Route tickets to agents with specific expertise.
Properties
| Name | Meaning |
|---|---|
| Dados (JSON) | JSON object containing the ticketId (ID of the ticket to transfer) and userId (ID of the target agent to receive the ticket). Example: {"ticketId": 123, "userId": 1} |
Output
The node outputs a JSON object representing the response from the Digitalsac API after attempting the transfer operation. The structure depends on the API but generally includes confirmation of success or details about any error encountered.
Example output JSON might include fields such as:
- Success status
- Updated ticket information
- Error messages if the transfer failed
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Digitalsac API.
- The node uses the base URL and token from these credentials to make HTTP requests.
- Proper configuration of the Digitalsac API credentials in n8n is necessary.
Troubleshooting
- Invalid JSON format: If the "Dados (JSON)" property contains malformed JSON, the node will throw an error "Formato de JSON inválido para Dados (JSON)". Ensure the JSON syntax is correct.
- Missing required fields: The JSON must include both
ticketIdanduserId. Omitting either may cause API errors. - API authentication errors: If the API token is invalid or expired, the request will fail. Verify the API key credential setup.
- Network issues: Connectivity problems can cause request failures; check network access to the Digitalsac API endpoint.
- Unexpected API responses: Errors returned by the API are included in the output under an
errorfield for diagnosis.
Links and References
- Digitalsac API Documentation (example link, replace with actual)
- n8n documentation on HTTP Request Node for understanding how API calls work within n8n nodes.