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 a list of services (Servicos). It is designed to fetch service data with optional filtering and pagination, making it useful for workflows that need to synchronize or process service information from the Trinks platform.

Common scenarios include:

  • Importing or syncing available services into another system.
  • Filtering services by name or category to trigger specific automation.
  • Retrieving only client-visible services for customer-facing applications.

For example, you could use this node to get all visible services in the "Spa" category on page 2 with a page size of 50, then process or display them elsewhere.

Properties

Name Meaning
Page The page number of results to retrieve (pagination).
Page Size Number of services to return per page.
Nome Filter services by their name. If empty, no name filter is applied.
Categoria Filter services by category. If empty, no category filter is applied.
Somente Visiveis Cliente If true, only services visible to clients are returned; if false, all services are retrieved.

Output

The node outputs an array of JSON objects representing the services retrieved from the API. Each item corresponds to one service with its details as provided by the Trinks API.

The output structure is:

[
  {
    "id": "...",
    "nome": "...",
    "categoria": "...",
    "visivelCliente": true,
    ...
  },
  ...
]

No binary data is output by this node.

Dependencies

  • Requires an API key credential and an establishment ID credential to authenticate requests to the Trinks API.
  • The base URL used is https://api.trinks.com.
  • The node sends requests with headers including Accept: application/json, Content-Type: application/json, and authentication headers.

Troubleshooting

  • Operation not found error: If the specified operation is incorrect or missing, the node will throw an error listing available operations. Ensure the operation name matches exactly "GET /v1/servicos".
  • Authentication errors: Missing or invalid API key or establishment ID credentials will cause request failures. Verify credentials are correctly configured.
  • Empty or unexpected responses: Check filter parameters; empty strings mean no filtering, so ensure filters are set as intended.
  • Pagination issues: If no results appear, verify that the Page and Page Size values are within valid ranges supported by the API.

Links and References

Discussion