TrinksInstall

Overview

This node integrates with the Trinks API to retrieve data related to clients and their tags. Specifically, for the operation GET /v1/clientes/{clienteId}/etiquetas, it fetches all tags associated with a particular client identified by their ID. This is useful in scenarios where you want to manage or analyze client metadata, segment clients based on tags, or synchronize client tag information with other systems.

Practical examples include:

• Fetching all tags of a client to personalize marketing campaigns.
• Synchronizing client tags from Trinks into a CRM system.
• Automating workflows based on client tag changes or presence.

Properties

Output

The node outputs an array of JSON objects, each representing the response from the Trinks API for the requested client tags. The structure corresponds directly to the API's JSON response for the endpoint /v1/clientes/{clienteId}/etiquetas. Typically, this will include details about each tag assigned to the client.

If the API returns binary data (not typical for this GET operation), it would be included accordingly, but here the output is purely JSON.

Example output snippet (conceptual):

[
  {
    "id": 123,
    "name": "VIP",
    "description": "High value client"
  },
  {
    "id": 456,
    "name": "Newsletter Subscriber",
    "description": "Subscribed to monthly newsletter"
  }
]

Dependencies

• Requires an API key credential and an establishment ID credential to authenticate requests to the Trinks API.
• The node uses the base URL https://api.trinks.com.
• Proper configuration of these credentials within n8n is necessary for successful API calls.

Troubleshooting

• Operation Not Found Error: If the specified operation is not recognized, ensure that the operation name exactly matches one of the supported operations. The error message will list available operations.
• Authentication Errors: If the API key or establishment ID is missing or invalid, the request will fail. Verify that credentials are correctly set up in n8n.
• Invalid Cliente Id: Providing a non-existent or incorrect client ID may result in empty responses or errors from the API.
• Network Issues: Connectivity problems can cause request failures; check network access to api.trinks.com.

Links and References

• Trinks API Documentation (hypothetical link for reference)
• n8n documentation on HTTP Request Node for understanding how API calls are made within n8n.