Press TicketInstall

Overview

This node integrates with the Press Ticket® API to manage various communication-related resources such as messages, contacts, tickets, queues, tags, WhatsApp connections, and sessions. Specifically, for the Ticket resource and the operation "Obter Ticket Aberto do Contato" (Get open ticket from a contact), it retrieves any open support or service tickets associated with a given contact ID.

This functionality is useful in customer support automation scenarios where you want to check if a contact currently has an open ticket before creating a new one or taking further action. For example, a helpdesk workflow can use this node to fetch open tickets of a customer to avoid duplicate requests or to escalate existing issues.

Properties

Output

The output is a JSON array containing the open ticket(s) related to the specified contact. The structure depends on the API response but typically includes ticket details such as ticket ID, status, assigned user, queue, timestamps, and other relevant metadata.

If multiple open tickets exist, each ticket will be an item in the output array. If no open tickets are found, the output may be empty or contain an object indicating no results.

No binary data is returned for this operation.

Dependencies

• Requires an API key credential for authenticating with the Press Ticket® API.
• The node uses the base URL and token from the configured credentials to make HTTP requests.
• No additional external dependencies beyond the Press Ticket® API and n8n's HTTP request helpers.

Troubleshooting

• Invalid Contact ID: If the provided contact ID does not exist or is malformed, the API may return an error or empty result. Verify the contact ID is correct.
• API Authentication Errors: Ensure the API token credential is valid and has sufficient permissions.
• Unexpected Response Format: The node expects the API to return either an array or an object containing ticket data. If the API changes, errors like "Formato de resposta inválido ao obter ticket aberto do contato" (Invalid response format when getting open ticket from contact) may occur.
• Network Issues: Connectivity problems to the Press Ticket® API endpoint will cause request failures.
• To handle errors gracefully, enable "Continue On Fail" in the node settings to prevent workflow interruption.

Links and References

• Press Ticket® Official Website (for general product info)
• Refer to your Press Ticket® API documentation for detailed information about ticket endpoints and authentication.