Trinks

Interact with Trinks API
Join our community

Actions8

Overview

This node integrates with the Trinks API to manage various resources such as customers, appointments, professionals, and services. Specifically, for the Professional - List operation, it retrieves a list of professionals from the Trinks system.

Common scenarios where this node is beneficial include:

  • Synchronizing professional data from Trinks into other systems or workflows.
  • Displaying available professionals in an internal dashboard.
  • Automating processes that depend on professional information, such as scheduling or notifications.

For example, you might use this node to fetch all professionals and then filter or route data based on their specialties or availability.

Properties

Name Meaning
Collect All Whether to return all results or only up to a given limit
Limit Max number of results to return (only used if "Collect All" is false)
  • Collect All: If set to true, the node will retrieve all professionals without limiting the number of results.
  • Limit: When "Collect All" is false, this property defines the maximum number of professionals to return.

Output

The output consists of an array of JSON objects, each representing a professional retrieved from the Trinks API. Each item contains the professional's details as provided by the API.

Example structure of one output item (simplified):

{
  "json": {
    "id": "string",
    "name": "string",
    "email": "string",
    "phone": "string",
    // ... other professional-specific fields returned by the API
  }
}

No binary data is output by this node.

Dependencies

  • Requires an active connection to the Trinks API using an API key credential configured in n8n.
  • The node uses a helper function to make authenticated HTTP requests to the Trinks API endpoints.
  • No additional external dependencies beyond the Trinks API and its authentication are needed.

Troubleshooting

  • Empty result set: If no professionals are returned, verify that your Trinks account has professionals registered and that your API credentials have sufficient permissions.
  • API errors: Errors from the Trinks API (e.g., authentication failures, rate limits) will be thrown as node errors. Ensure your API key is valid and has not expired.
  • Limit ignored when Collect All is true: The "Limit" property is only respected when "Collect All" is false; otherwise, all records are fetched.
  • Network issues: Connectivity problems can cause request failures. Check your network and proxy settings if applicable.

Links and References

Discussion