Press Ticket icon

Press Ticket

Interage com a API do Press Ticket®
Join our community

Actions32

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 with the Obter (Get) operation, it retrieves detailed information about a specific ticket by its ID.

Common scenarios where this node is beneficial include:

  • Fetching ticket details to display or process in workflows.
  • Automating customer support processes by retrieving ticket status or metadata.
  • Integrating ticket data into other systems for reporting or follow-up actions.

Practical example:

  • A workflow that triggers when a new message arrives, then uses this node to get the associated ticket details by ticket ID to decide the next steps based on ticket status.

Properties

Name Meaning
ID do Ticket The unique identifier of the ticket to be retrieved or updated.

Output

The output is a JSON array containing the ticket details as returned by the Press Ticket® API. The structure typically includes all relevant fields of the ticket such as ID, status, contact ID, assigned user, queue, timestamps, and any other metadata provided by the API.

No binary data output is produced for this operation.

Example output snippet (conceptual):

{
  "id": "12345",
  "status": "open",
  "contactId": "67890",
  "queueId": "1",
  "userId": "42",
  "createdAt": "2024-01-01T12:00:00Z",
  "updatedAt": "2024-01-02T15:30:00Z"
}

Dependencies

  • Requires an API key credential for authenticating with the Press Ticket® API.
  • The node configuration must include the API base URL and the API token.
  • Network access to the Press Ticket® API endpoints.

Troubleshooting

  • Invalid Ticket ID: If the provided ticket ID does not exist or is malformed, the API may return an error or empty response. Verify the ticket ID correctness.
  • Authentication Errors: Ensure the API token credential is valid and has sufficient permissions.
  • API Response Format Issues: Unexpected response formats may cause errors; ensure the API version matches the node expectations.
  • Network Issues: Connectivity problems can cause request failures; check network and firewall settings.

Common error message example:

  • "Formato de resposta inválido ao obter ticket" — indicates the API response was not in the expected format; verify API availability and credentials.

Links and References

Discussion