Trinks icon

Trinks

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

Actions46

Overview

This node integrates with the Trinks API to retrieve product data. Specifically, for the resource "Produtos" and operation "GET /v1/produtos", it fetches a paginated list of products optionally filtered by name. This is useful in scenarios where you want to synchronize product catalogs, display product lists, or automate inventory checks within n8n workflows.

Practical examples include:

  • Fetching all products page by page to update an external database.
  • Searching for products by name to trigger notifications or further processing.
  • Integrating product data into marketing or sales automation pipelines.

Properties

Name Meaning
Page The page number of the product list to retrieve (pagination).
Page Size The number of products to return per page (pagination size).
Nome Filter products by their name (partial or full match).

Output

The node outputs JSON data representing the response from the Trinks API for the requested products. The structure typically includes product details such as IDs, names, descriptions, prices, and other relevant fields as provided by the API.

Each output item corresponds to one input item processed, containing a json property with the API response data.

No binary data output is produced by this node.

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.

Troubleshooting

  • Common issues:

    • Invalid or missing API key or establishment ID will cause authentication failures.
    • Requesting pages beyond available data may return empty results.
    • Incorrect property values (e.g., negative page numbers) might lead to unexpected API responses.

  • Error messages:

    • If the specified operation is not found, the node logs available operations and throws an error indicating the operation is invalid.
    • Network or API errors will be thrown unless "Continue On Fail" is enabled, in which case errors are returned in the output JSON under an error field.

  • Resolution tips:

    • Verify that API credentials are correctly configured in n8n.
    • Ensure pagination parameters are within valid ranges.
    • Use the exact operation string "GET /v1/produtos" when configuring the node.

Links and References

Discussion