Digitalsac Izing ProInstall

Overview

This node integrates with the Digitalsac API, providing various operations to manage tickets, tags, messaging, scheduling, and more within the Digitalsac platform. Specifically, the "Vincular Tag" (Link Tag) operation allows users to link a tag to a ticket by sending the ticket ID and tag ID in JSON format.

Common scenarios for this node include automating customer support workflows, tagging tickets for categorization, transferring tickets between queues or agents, sending messages via WhatsApp, managing schedules, and interacting with other Digitalsac resources.

Practical example:
You have an incoming support ticket and want to automatically assign a specific tag to it based on certain criteria. Using this node's "Vincular Tag" operation, you can programmatically link the appropriate tag to the ticket, enabling better organization and reporting.

Properties

Output

The node outputs an array of JSON objects corresponding to each input item processed. Each output JSON contains the response from the Digitalsac API for the requested operation.

For the "Vincular Tag" operation, the output JSON will typically contain confirmation details or status about the tag linking action performed on the specified ticket.

If an error occurs during the API request, the output JSON will contain an error field describing the issue.

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.
• No additional external dependencies are required beyond the Digitalsac API access.

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 is correctly formatted.
• API authentication errors: If the API token is invalid or missing, requests will fail. Verify that the API key credential is properly configured.
• Missing required fields: For "Vincular Tag", ensure both ticketId and tagId are provided in the JSON input.
• Network or API errors: Errors returned by the Digitalsac API will be included in the output under the error field. Review the message for troubleshooting.

Links and References

• Digitalsac API Documentation (Assumed official API docs; replace with actual if available)
• n8n Documentation on Creating Custom Nodes