Press Ticket icon

Press Ticket

Interage com a API do Press Ticket®

Overview

This node integrates with the Press Ticket® API to manage various resources such as messages, contacts, tickets, tags, WhatsApp connections, sessions, and queues (sectors). Specifically, for the Setor (Queue) resource with the Atualizar (Update) operation, it updates an existing sector's details by sending a PUT request to the API.

Use cases include updating the name or color of a sector in your ticketing or communication system managed via Press Ticket®. For example, if you want to rename a department or change its associated color code for better visual identification, this node operation facilitates that update seamlessly.

Properties

Name Meaning
ID do Setor The unique identifier of the sector (queue) to be updated.
Nome The new name to assign to the sector.
Cor The new color for the sector, specified in hexadecimal format (e.g., #FF0000 for red).

Output

The node outputs a JSON object representing the updated sector as returned by the Press Ticket® API. This typically includes the sector's ID, updated name, color, and possibly other metadata provided by the API response.

Example output structure (simplified):

{
  "id": "123",
  "name": "New Sector Name",
  "color": "#FF0000"
}

No binary data is output by this operation.

Dependencies

  • Requires an active connection to the Press Ticket® API.
  • Needs an API authentication token credential configured in n8n to authorize requests.
  • The node uses HTTP methods (PUT) to interact with the API endpoint /v1/queue/{queueId}.

Troubleshooting

  • Common issues:

    • Invalid or missing sector ID (queueId) will cause the API to reject the update request.
    • Incorrect color format (not a valid hex code) may result in validation errors from the API.
    • Network or authentication failures if the API token is invalid or expired.
  • Error messages:

    • "Invalid queue ID" or similar indicates the sector does not exist or the ID is wrong.
    • "Unauthorized" or "Invalid API token" means the credentials need to be checked or refreshed.
    • "Failed to process response" could occur if the API returns unexpected data; ensure the API is reachable and stable.
  • Resolution tips:

    • Verify the sector ID exists before attempting an update.
    • Confirm the color string is a valid hex code starting with #.
    • Check API credentials and permissions.
    • Enable "Continue on Fail" in the node settings to handle errors gracefully during batch operations.

Links and References

Discussion