TrinksInstall

Overview

This node integrates with the Trinks API, specifically allowing users to interact with the "Etiquetas" (Tags) resource. The GET /v1/etiquetas operation fetches a paginated list of etiquetas (tags) from the Trinks system.

Typical use cases include:

• Retrieving tags for filtering or categorizing appointments, clients, or services within an automation workflow.
• Synchronizing etiquetas data from Trinks into other systems or databases.
• Building dynamic lists or reports based on etiquetas metadata.

For example, a user might want to fetch etiquetas page by page to process or display them in batches, or to update local records with the latest tag information from Trinks.

Properties

Output

The node outputs JSON data representing the response from the Trinks API for the etiquetas list request. The structure corresponds directly to the API's response schema for the GET /v1/etiquetas endpoint, typically including:

• An array or list of etiqueta objects, each representing a tag with its properties.
• Pagination metadata such as total count, current page, and page size (if provided by the API).

No binary data output is produced by this node.

Example output snippet (conceptual):

{
  "items": [
    {
      "id": "string",
      "name": "string",
      "description": "string"
      // other etiqueta fields...
    }
  ],
  "page": 1,
  "pageSize": 20,
  "totalItems": 100
}

Dependencies

• Requires an API key credential and an establishment ID credential to authenticate requests to the Trinks API.
• The base URL for API requests is https://api.trinks.com.
• The node sets HTTP headers including Accept: application/json, Content-Type: application/json, X-Api-Key, and estabelecimentoId for authentication and identification.
• No additional external dependencies beyond the Trinks API and n8n's HTTP request helper.

Troubleshooting

• Common issues:

  • Invalid or missing API key or establishment ID will cause authentication failures.
  • Requesting pages beyond the available range may return empty results or errors.
  • Network connectivity issues can prevent successful API calls.

• Error messages:

  • "Operation ... not found": Indicates the specified operation name is invalid or misspelled.
  • HTTP errors from the API (e.g., 401 Unauthorized, 404 Not Found) usually indicate credential or endpoint issues.

• Resolutions:

  • Verify that the API key and establishment ID credentials are correctly configured in n8n.
  • Confirm the operation and resource names match exactly as expected.
  • Check network access and API availability.
  • Use valid pagination parameters (Page and Page Size) within allowed ranges.

Links and References

• Trinks API Documentation (general reference for API endpoints and authentication)
• n8n Documentation on Creating Custom Nodes