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 (sectors), tags, WhatsApp connections, and WhatsApp sessions. Specifically for the Setor (Queue) resource with the Criar (Create) operation, it allows users to create a new sector by specifying its name and color.

Common scenarios where this node is beneficial include automating customer support workflows, managing communication tickets, organizing contacts and tags, and handling WhatsApp messaging and connections within an automated workflow environment.

Practical example:
You can use this node to automatically create a new support sector (queue) in your Press Ticket system when onboarding a new department or team, assigning it a specific color for easy identification in the interface.

Properties

Name Meaning
Nome The name of the sector (queue) to be created.
Cor The color of the sector in hexadecimal format (e.g., #000000 for black).

Output

The output is a JSON array containing the response from the Press Ticket API after creating the sector. This typically includes details of the newly created sector such as its ID, name, color, and other metadata returned by the API.

No binary data output is involved in this operation.

Dependencies

  • Requires an API key credential for authenticating with the Press Ticket® API.
  • The node uses the base API URL and token obtained from these credentials.
  • Network access to the Press Ticket® API endpoint is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing API authentication token will cause request failures.
    • Providing invalid color codes (not in hexadecimal format) may result in API errors.
    • Missing required parameters like "Nome" or "Cor" will prevent successful creation.

  • Error messages:

    • Errors from the API are propagated; typical messages might indicate authentication failure, validation errors on input fields, or network connectivity problems.
    • If the node throws an error about missing parameters, ensure all required fields are filled correctly.

  • Resolution tips:

    • Verify that the API key credential is correctly configured and has sufficient permissions.
    • Double-check the color value format.
    • Use the "Continue On Fail" option in n8n if you want the workflow to proceed despite individual item errors.

Links and References

  • Press Ticket® Official Website (for general product info)
  • Press Ticket® API documentation (not publicly linked here; consult your Press Ticket® account or support for API docs)

Discussion