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 tags within the system. Specifically, the "Atualizar" (Update) operation for the "Tag" resource allows users to update an existing tag's name and color by specifying its ID. This is useful in scenarios where you want to rename a tag or change its associated color to better organize or categorize items such as contacts or tickets.

Practical examples include:

  • Renaming a tag from "Urgent" to "High Priority".
  • Changing the color of a tag to visually differentiate it in the user interface.

Properties

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

Output

The output is a JSON object representing the updated tag as returned by the Press Ticket® API. It typically includes fields such as the tag's ID, updated name, color, and possibly other metadata related to the tag.

Example output structure (simplified):

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

No binary data output is involved in this operation.

Dependencies

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

Troubleshooting

  • Invalid Tag ID: If the provided tag ID does not exist, the API may return an error indicating the tag was not found. Verify the tag ID before running the node.
  • Invalid Color Format: The color must be in hexadecimal format. Providing an invalid color string may cause the API to reject the request.
  • Authentication Errors: Ensure that the API token credential is correctly set up and has sufficient permissions.
  • API Endpoint Issues: Network issues or incorrect API URL configuration can cause request failures. Confirm the API URL is correct in the credentials.
  • 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