Trinks

Interact with Trinks API
Join our community

Actions8

Overview

This node integrates with the Trinks API to manage appointments. Specifically, the Appointment - List operation retrieves a list of appointments from the Trinks system. It supports filtering appointments by start and end dates and allows either fetching all matching appointments or limiting the number of results returned.

Common scenarios where this node is beneficial include:

  • Synchronizing appointment data from Trinks into other systems.
  • Generating reports or dashboards based on appointment schedules within a specific date range.
  • Automating workflows that depend on upcoming or past appointments.

For example, you could use this node to fetch all appointments scheduled for the next week to send reminder emails or to analyze appointment trends over time.

Properties

Name Meaning
Collect All Whether to return all matching appointments or only up to a specified limit.
Limit Maximum number of appointments to return (used only if "Collect All" is false).
Start Date Filter to include only appointments starting on or after this date/time (format: YYYY-MM-DD HH:MM:SS).
End Date Filter to include only appointments ending on or before this date/time (format: YYYY-MM-DD HH:MM:SS).

Output

The output consists of an array of JSON objects, each representing an appointment retrieved from the Trinks API. Each object contains the appointment's details as provided by the API, such as identifiers, customer info, professional info, service info, start time, status, and any other metadata included in the API response.

No binary data is output by this operation.

Dependencies

  • Requires an active connection to the Trinks API via an API key credential configured in n8n.
  • The node uses a helper function to make authenticated HTTP requests to the Trinks API endpoints.
  • Proper API permissions are needed to list appointments.

Troubleshooting

  • Empty results: If no appointments are returned, verify the date filters and ensure there are appointments in the specified range.
  • API errors: Errors from the Trinks API (e.g., authentication failures, rate limits) will be surfaced as node execution errors. Check your API credentials and quota.
  • Invalid date format: Ensure that the Start Date and End Date inputs follow the required format (YYYY-MM-DD HH:MM:SS).
  • Limit ignored: If "Collect All" is set to true, the "Limit" property is ignored and all matching appointments are fetched, which may lead to longer execution times or API rate limits.

Links and References

Discussion