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 to interact with tickets, kanbans, tags, queues, agents, messages, schedules, and more within the Digitalsac platform. Specifically, the "Vincular Kanban" (Link Kanban) operation allows you to link a ticket to a kanban board for better task or issue tracking.
Common scenarios where this node is beneficial include automating customer support workflows, managing tickets and their statuses via kanban boards, sending messages or media through WhatsApp connections, scheduling appointments, and organizing service queues.
For example, using the "Vincular Kanban" operation, you can automatically associate a support ticket with a specific kanban board column or card, helping teams visualize and manage ticket progress seamlessly.
Properties
| Name | Meaning |
|---|---|
| Dados (JSON) | JSON object containing IDs required to link a ticket to a kanban: ticketId, kanbanId, and userId. Example: {"ticketId": 123, "kanbanId": 456, "userId": 789} |
Output
The node outputs an array of JSON objects, each representing the response from the Digitalsac API for the executed operation. For the "Vincular Kanban" operation, the output JSON will typically contain confirmation details about the linking action, such as success status or any returned data from the API.
If an error occurs during the API request, the output JSON will contain an error field describing the issue.
The node does not output binary data for this operation.
Dependencies
- Requires an API key credential for authenticating with the Digitalsac API.
- The node uses HTTP requests to communicate with the Digitalsac API endpoints.
- Proper configuration of the API base URL and token is necessary in the credentials setup.
- Input JSON data must be correctly formatted; otherwise, the node will throw a JSON parsing error.
Troubleshooting
- Invalid JSON Format: If the "Dados (JSON)" property contains malformed JSON, the node throws an error "Formato de JSON inválido para Dados (JSON)". Ensure the JSON syntax is correct before running the node.
- Missing Required Fields: The JSON must include
ticketId,kanbanId, anduserId. Omitting these may cause API errors or unexpected behavior. - API Authentication Errors: If the API token is invalid or missing, requests will fail. Verify that the API key credential is correctly configured.
- Network or API Errors: Any HTTP errors or API response errors are captured and returned in the output's
errorfield. Check the error message for troubleshooting. - Empty or Incorrect Response: If the API endpoint changes or is unavailable, the node might return unexpected results. Confirm the API endpoint and parameters are up to date.
Links and References
- Digitalsac API Documentation (Assumed official API docs, replace with actual if available)
- n8n Documentation on Creating Custom Nodes
- JSON Validator tools for verifying input JSON syntax (e.g., https://jsonlint.com/)