TrinksInstall

Overview

This node integrates with the Trinks API to retrieve financial transaction data. Specifically, for the Financeiro Transacoes resource and the GET /v1/transacoes operation, it fetches a paginated list of transactions within an optional date range and can include or exclude reversed transactions.

Common scenarios where this node is beneficial include:

• Financial reporting and reconciliation by fetching transaction records.
• Auditing transactions over specific periods.
• Integrating transaction data into other workflows or dashboards.

For example, a user might configure this node to get all transactions from the start to the end of a month, with pagination controls to handle large datasets, optionally including reversed transactions for completeness.

Properties

Output

The node outputs JSON data representing the response from the Trinks API for the requested transactions. Each item in the output corresponds to one API response for an input item.

The structure of the JSON output depends on the API's response but generally includes transaction details such as IDs, dates, amounts, statuses, and possibly metadata about pagination.

No binary data output is produced by this node.

Example output snippet (simplified):

{
  "transactions": [
    {
      "id": "12345",
      "date": "2023-01-15",
      "amount": 100.00,
      "status": "completed",
      ...
    },
    ...
  ],
  "page": 1,
  "pageSize": 50,
  "totalPages": 10
}

Dependencies

• Requires an API key credential and an establishment ID credential to authenticate requests to the Trinks API.
• The node sends HTTP requests to https://api.trinks.com.
• No additional external dependencies beyond the configured credentials and network access to the API endpoint.

Troubleshooting

• Common issues:

  • Invalid or missing API key or establishment ID will cause authentication failures.
  • Incorrect date formats for Data Inicio or Data Fim may lead to API errors or empty results.
  • Pagination parameters (Page, Page Size) set incorrectly could result in no data or repeated data.

• Error messages:

  • "Operation ... not found": This indicates an invalid operation name was specified; ensure the operation matches exactly GET /v1/transacoes.
  • Network or authentication errors will typically be returned from the API and surfaced in the node's error output.

• Resolutions:

  • Verify that the API key and establishment ID are correctly configured in the node credentials.
  • Use ISO 8601 date format strings for date filters.
  • Adjust pagination parameters to valid ranges supported by the API.

Links and References

• Trinks API Documentation (hypothetical link)
• n8n documentation on HTTP Request Node for understanding request handling
• General API pagination best practices: https://swagger.io/docs/specification/2-0/describing-parameters/#query-parameters