TrinksInstall

Overview

This node integrates with the Trinks API to manage client tags (etiquetas) associated with clients (clientes). Specifically, the DELETE operation for the resource "Clientes Etiquetas" removes a tag from a specified client by their respective IDs. This is useful in scenarios where you want to dynamically update or clean up client metadata by removing outdated or incorrect tags.

Practical examples include:

• Removing promotional tags from clients who no longer qualify.
• Cleaning up client profiles by deleting obsolete category labels.
• Automating client segmentation updates based on changing business rules.

Properties

Output

The node outputs JSON data representing the response from the Trinks API after attempting to delete the specified tag from the client. The structure depends on the API's response but typically includes confirmation of deletion or error details.

If an error occurs and the node is configured to continue on failure, the output JSON will contain an error field with the error message.

No binary data output is produced by this operation.

Dependencies

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

Troubleshooting

• Common issues:

  • Invalid or missing Cliente Id or Etiqueta Id parameters may cause the API to reject the request.
  • Incorrect or expired API key or establishment ID credentials will result in authentication errors.
  • Network connectivity problems can prevent successful API calls.

• Error messages:

  • "Operation ... not found": Indicates that the specified operation string does not match any available operations; ensure the correct operation name is used.
  • API errors returned in the JSON response will be passed through; check the error message for details such as "Tag not found" or "Client not found".

• Resolutions:

  • Verify that both Cliente Id and Etiqueta Id are correctly set and correspond to existing entities.
  • Confirm that API credentials are valid and have necessary permissions.
  • Enable "Continue On Fail" if you want the workflow to proceed despite individual item failures and handle errors gracefully.

Links and References

• Trinks API Documentation (general reference for API endpoints and authentication)
• n8n documentation on HTTP Request Node for understanding how API calls are made within nodes.