TrinksInstall

Overview

This node integrates with the Trinks API, specifically to interact with the "Financeiro Formas Pagamento" resource and perform the operation GET /v1/formaspagamentos. It retrieves payment method data from the financial module of the Trinks system. This is useful for workflows that need to fetch available payment methods, for example, to synchronize them with another system, generate reports, or validate payment options dynamically.

Practical examples:

• Fetching a paginated list of payment methods to display in a dashboard.
• Automating synchronization of payment methods between Trinks and an accounting system.
• Using payment method data as part of a larger booking or sales workflow.

Properties

These properties are sent as query parameters in the API request to control pagination of the returned payment methods.

Output

The node outputs JSON data representing the response from the Trinks API for the payment methods endpoint. The structure corresponds directly to the API's response schema for /v1/formaspagamentos, typically including an array of payment method objects along with pagination metadata.

If the API supports binary data in other operations, this node does not output binary data for this specific operation.

Example output JSON snippet (conceptual):

{
  "data": [
    {
      "id": "string",
      "name": "string",
      "active": true,
      ...
    }
  ],
  "page": 1,
  "pageSize": 10,
  "totalCount": 100
}

Dependencies

• Requires an API key credential and an establishment ID credential configured in n8n to authenticate requests to the Trinks API.
• The node uses the base URL https://api.trinks.com.
• The HTTP headers include Accept: application/json and Content-Type: application/json.

Troubleshooting

• Common issues:

  • Missing or invalid API key or establishment ID will cause authentication errors.
  • Providing invalid pagination values (e.g., negative numbers) may result in API errors or empty responses.
  • Network connectivity issues can cause request failures.

• Error messages:

  • "Operation ... not found": Indicates the specified operation name is incorrect or unsupported.
  • API error responses will be passed through; check the message for details such as unauthorized access or invalid parameters.

• Resolutions:

  • Verify credentials are correctly set up and valid.
  • Ensure pagination parameters are within allowed ranges.
  • Check network connectivity and API availability.

Links and References

• Trinks API Documentation (general reference for API endpoints and schemas)
• n8n documentation on HTTP Request Node for understanding how API calls are made under the hood.