Trinks icon

Trinks

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

Actions46

Overview

This node integrates with the Trinks API, specifically allowing users to interact with various resources and operations exposed by Trinks. The selected operation here is GET /v1/clientes/{clienteId}/etiquetas/{etiquetaId}, which retrieves a specific label (etiqueta) associated with a particular client (cliente).

Typical use cases include:

  • Fetching detailed information about a client's label in a salon or service management context.
  • Automating workflows that require retrieving client-specific tags or labels for segmentation, marketing, or reporting.
  • Integrating client label data into other systems or dashboards.

For example, a salon manager could use this node to automatically pull label details for a client before sending personalized promotions.

Properties

Name Meaning
Cliente Id The unique numeric identifier of the client whose label you want to retrieve.
Etiqueta Id The unique numeric identifier of the label (etiqueta) assigned to the specified client.

Output

The node outputs JSON data representing the label details retrieved from the Trinks API for the given client and label IDs. The structure corresponds directly to the API response for the endpoint /v1/clientes/{clienteId}/etiquetas/{etiquetaId} and typically includes fields describing the label's properties.

If the request fails and "Continue On Fail" is enabled, the output will contain an error object with a message describing the failure.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Trinks API.
  • Needs the establishment ID credential value as part of the request headers.
  • The node uses the base URL https://api.trinks.com.
  • Proper configuration of these credentials in n8n is necessary for successful requests.

Troubleshooting

  • Operation Not Found Error: If the specified operation string does not match any available operation, the node throws an error listing valid operations. Ensure the operation name matches exactly.
  • Authentication Errors: Missing or invalid API key or establishment ID will cause authentication failures. Verify credentials are correctly set up.
  • Parameter Replacement Issues: The URL template placeholders ({{$parameter["..."]}}) must be replaced with valid input parameters. Supplying invalid or missing clienteId or etiquetaId will result in request errors.
  • Network or API Errors: Standard HTTP errors from the Trinks API (e.g., 404 if label not found) will be returned in the node output or cause execution to fail unless "Continue On Fail" is enabled.

Links and References

Discussion