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 Service - List operation, it retrieves a list of available services from the Trinks platform.

This node is beneficial when you want to automate workflows that require fetching service data from Trinks, such as syncing services with other systems, displaying available services in dashboards, or triggering actions based on service availability.

Example use cases:

  • Automatically retrieve all services offered by a business to update an external booking system.
  • Fetch a limited number of services to display in a custom UI or report.
  • Integrate service data into marketing automation workflows.

Properties

Name Meaning
Collect All Whether to return all available service results or only up to a specified limit.
Limit Maximum number of service results to return (used only if "Collect All" is false).

Output

The node outputs an array of JSON objects, each representing a service retrieved from the Trinks API. Each JSON object contains the service details as provided by the API, such as service ID, name, description, price, duration, and other relevant attributes.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Trinks API using an API key credential configured in n8n.
  • The node uses the Trinks API endpoints to fetch service data (GET /v1/servicos).
  • Proper network access and valid authentication credentials are necessary.

Troubleshooting

  • Common issues:

    • Authentication errors due to invalid or missing API credentials.
    • Network connectivity problems preventing access to the Trinks API.
    • API rate limits or quota exceeded errors.
    • Unexpected empty results if no services exist or filters exclude all entries.

  • Error messages:

    • Operation list on resource service not implemented: This indicates a misconfiguration or unsupported operation/resource combination; ensure the node parameters are correctly set to "Service" and "List".
    • API response errors will typically be passed through; check the error message for details such as unauthorized access or invalid parameters.

  • Resolutions:

    • Verify API credentials and permissions.
    • Check network connectivity and firewall settings.
    • Confirm that the Trinks account has services configured.
    • Adjust "Collect All" and "Limit" parameters appropriately.

Links and References

Discussion