Trinks icon

Trinks

Nó N8N para interagir com a API do Trinks
Join our community

Actions46

Overview

This node integrates with the Trinks API to update an existing "Etiqueta" (label/tag) resource by its ID. Specifically, it performs a PUT request to the endpoint /v1/etiquetas/{etiquetaId}, allowing users to modify the content and color of a label.

Common scenarios for this node include:

  • Updating label details in a CRM or booking system that uses Trinks.
  • Changing tag colors or descriptions dynamically based on workflow conditions.
  • Automating label management as part of customer segmentation or categorization workflows.

For example, a user might update a label's content to reflect a new campaign name or change its color to indicate priority status.

Properties

Name Meaning
Etiqueta Id The unique numeric identifier of the label to update.
Conteudo The new content/text of the label.
Cor The new color value for the label.

Output

The node outputs the JSON response returned by the Trinks API after updating the label. This typically includes the updated label object with its properties such as id, content, color, and possibly metadata about the update.

If the API returns binary data (not indicated here), it would be summarized accordingly, but this operation deals with JSON data only.

Dependencies

  • Requires an API key credential and an establishment ID credential for authenticating requests to the Trinks API.
  • The base URL used is https://api.trinks.com.
  • The node sends requests with headers including Accept: application/json, Content-Type: application/json, and authentication headers containing the API key and establishment ID.

Troubleshooting

  • Operation Not Found Error: If the specified operation string does not match any available operations, the node will throw an error listing valid operations. Ensure the operation name matches exactly.
  • Authentication Errors: Missing or invalid API key or establishment ID credentials will cause authentication failures. Verify credentials are correctly configured.
  • Invalid Etiqueta Id: Providing a non-existent or incorrect label ID will result in API errors. Confirm the label ID exists before updating.
  • Empty Required Fields: The Etiqueta Id is required; omitting it will cause errors. Also, ensure that at least one of Conteudo or Cor is provided to update.
  • API Rate Limits or Network Issues: Standard HTTP errors may occur due to rate limiting or connectivity problems. Implement retry logic or check network status if needed.

Links and References

Discussion