Trinks

Interact with Trinks API
Join our community

Actions8

Overview

This node integrates with the Trinks API to manage customers, appointments, professionals, and services. Specifically, for the Customer - List operation, it retrieves a list of customers from the Trinks system. This is useful in scenarios where you want to synchronize customer data, display customer lists, or process customer information within an n8n workflow.

For example, you might use this node to:

  • Fetch all customers to export them to another CRM.
  • Retrieve a limited number of customers for reporting or analytics.
  • Automate follow-up emails by iterating over customer records.

Properties

Name Meaning
Collect All Whether to return all customer results or only up to a given limit.
Limit Max number of customer results to return (only used if "Collect All" is false).

Output

The output is an array of JSON objects, each representing a customer retrieved from the Trinks API. Each item contains customer details as provided by the API, such as name, email, and other customer-specific fields.

No binary data is output by this operation.

Example output structure (simplified):

[
  {
    "json": {
      "id": "123",
      "nome": "John Doe",
      "email": "john.doe@example.com",
      ...
    }
  },
  {
    "json": {
      "id": "124",
      "nome": "Jane Smith",
      "email": "jane.smith@example.com",
      ...
    }
  }
]

Dependencies

  • Requires an API key credential for authenticating with the Trinks API.
  • The node uses a helper function to make HTTP requests to the Trinks API endpoints.
  • No additional external dependencies beyond the configured API authentication.

Troubleshooting

  • Empty result set: If no customers are returned, verify that your Trinks account has customers and that the API credentials have sufficient permissions.
  • API errors: Errors from the Trinks API (e.g., authentication failure, rate limits) will be thrown as node errors. Check your API key validity and usage limits.
  • Limit ignored when "Collect All" is true: When "Collect All" is enabled, the node ignores the "Limit" property and fetches all available customers, which may lead to longer execution times or large payloads.
  • Network issues: Ensure that your n8n instance can reach the Trinks API endpoint without firewall or proxy restrictions.

Links and References

Discussion