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 - Create operation, it allows users to create a new support or service ticket associated with a contact.

Typical use cases include:

  • Automatically creating a support ticket when a customer sends a message.
  • Logging issues or requests from contacts into a ticketing system.
  • Assigning tickets to specific departments (queues) or users for follow-up.

For example, you can create a ticket for a contact with a status of "open" and optionally assign it to a department and user, enabling structured tracking and resolution workflows.

Properties

Name Meaning
ID do Contato The ID of the contact for whom the ticket will be created.
Status The status of the ticket. Options: "Aberto" (open), "Pendente" (pending), "Fechado" (closed).
ID do Setor (Optional) The ID of the department/queue to which the ticket will be assigned.
ID do Usuário (Optional) The ID of the user to whom the ticket will be assigned.

Output

The node outputs an array of JSON objects representing the response from the Press Ticket® API after creating the ticket. The structure typically includes details of the newly created ticket such as its unique identifier, status, associated contact, assigned queue and user if provided, timestamps, and other metadata returned by the API.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Press Ticket® API.
  • The node expects the API URL and token to be configured in the credentials.
  • Network access to the Press Ticket® API endpoint is necessary.

Troubleshooting

  • Missing required fields: Ensure that the "ID do Contato" and "Status" properties are provided; these are mandatory.
  • Invalid IDs: Providing non-existent contact, queue, or user IDs may cause API errors.
  • Authentication errors: Verify that the API token credential is valid and has sufficient permissions.
  • API response format errors: If the API returns unexpected data, check for changes in the API or network issues.
  • Continue on Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error messages in the output.

Links and References

Discussion