Digitalsac Izing Pro icon

Digitalsac Izing Pro

Interage com a API do Digitalsac
Join our community

Actions23

Overview

This node integrates with the Digitalsac API, providing a variety of operations to interact with customer support tickets, queues, agents, messaging, tags, schedules, and more. Specifically, the "Transferir para Fila" (Transfer to Queue) operation allows transferring a support ticket to a different queue within the Digitalsac system.

Common scenarios for this node include automating ticket management workflows such as validating user data, sending messages or media via WhatsApp, managing tags and kanbans, scheduling appointments, and transferring tickets between queues or agents. For example, you could use the "Transferir para Fila" operation to automatically route a customer support ticket to the appropriate team based on certain criteria.

Properties

Name Meaning
Dados (JSON) JSON object containing the IDs required for the transfer: ticketId (ID of the ticket) and queueId (ID of the destination queue). Example: {"ticketId": 123, "queueId": 1}

Output

The node outputs an array of JSON objects, each representing the response from the Digitalsac API for the executed operation. The structure depends on the specific API endpoint called but generally contains the result or status of the requested action.

For the "Transferir para Fila" operation, the output JSON will typically include confirmation details about the ticket transfer, such as success status or error information if the transfer failed.

This node does not output binary data.

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.
  • Network access to the Digitalsac API endpoints is necessary.

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.
  • API Authentication Errors: If the API key or token is missing or invalid, requests will fail. Verify that the credential is correctly set up and has proper permissions.
  • Missing Required Fields: The JSON must include both ticketId and queueId. Omitting these or using incorrect types may cause API errors.
  • Network Issues: Connectivity problems to the Digitalsac API will result in request failures. Check network settings and API availability.
  • Unexpected API Responses: The node captures API errors and returns them in the output JSON under an error field. Review these messages to diagnose issues.

Links and References

Discussion