TrinksInstall

Overview

This node integrates with the Trinks API to manage client tags (etiquetas) by associating a specific tag with a client. The particular operation POST /v1/clientes/{clienteId}/etiquetas/{etiquetaId} adds or links a tag identified by etiquetaId to a client identified by clienteId. This is useful in scenarios where you want to categorize or label clients dynamically within your workflow, such as marking VIP customers, segmenting clients for marketing campaigns, or tracking client statuses.

Practical examples:

• Automatically tagging new clients who meet certain criteria.
• Adding promotional tags to clients after a purchase.
• Organizing clients into groups based on behavior or preferences.

Properties

Output

The node outputs the JSON response returned by the Trinks API after performing the tag assignment. This typically includes confirmation details about the association between the client and the tag. The output is structured as:

{
  // API response fields confirming the tag assignment
}

No binary data output is produced by this node.

Dependencies

• Requires an API key credential for authenticating with the Trinks API.
• Needs the establishment ID as part of the request headers, provided via credentials.
• The node sends HTTP requests to https://api.trinks.com.
• Proper configuration of the API key and establishment ID in n8n credentials is mandatory.

Troubleshooting

• Common issues:

  • Invalid or missing clienteId or etiquetaId values may cause the API to reject the request.
  • Incorrect or expired API key or establishment ID 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 operation name is correct.
  • API error responses will be passed through in the node's output under an error field if "Continue On Fail" is enabled.

• Resolutions:

  • Verify that both Cliente Id and Etiqueta Id are valid numbers corresponding to existing entities in Trinks.
  • Check that the API key and establishment ID credentials are correctly set up and have necessary permissions.
  • Enable "Continue On Fail" to handle errors gracefully during batch processing.

Links and References

• Trinks API Documentation (general reference for API endpoints)
• n8n documentation on HTTP Request Node for understanding underlying request mechanics (conceptual)