Trinks icon

Trinks

Nó N8N para interagir com a API do Trinks
Join our community

Actions46

Overview

This node integrates with the Trinks API to retrieve scheduling data ("Agendamentos"). Specifically, the GET /v1/agendamentos operation fetches a list of appointments or bookings based on optional filtering criteria such as client ID and date range. This node is useful for automating workflows that require access to appointment data, such as syncing schedules with calendars, generating reports, or triggering notifications based on upcoming bookings.

Practical examples:

  • Fetch all appointments for a specific client within a date range.
  • Paginate through large sets of booking data to process them in batches.
  • Integrate appointment data into CRM or marketing automation tools.

Properties

Name Meaning
Page The page number of results to retrieve (pagination).
Page Size Number of items per page to return (pagination size).
Cliente Id Filter results by a specific client ID.
Data Inicio Start date filter to retrieve appointments from this date onwards (format: string).
Data Fim End date filter to retrieve appointments up to this date (format: string).

Output

The node outputs an array of JSON objects representing the retrieved appointments. Each item corresponds to one appointment record returned by the API. The exact structure depends on the Trinks API response but typically includes details like appointment ID, client information, date/time, service details, and status.

No binary data output is produced by this node.

Example output snippet (conceptual):

[
  {
    "id": 123,
    "clientId": 456,
    "date": "2024-05-01T10:00:00Z",
    "service": "Haircut",
    "status": "confirmed"
  },
  ...
]

Dependencies

  • Requires an API key credential and an establishment ID credential configured in n8n to authenticate requests to the Trinks API.
  • The node sends HTTP requests to https://api.trinks.com.
  • The node expects the credentials to provide the necessary headers (X-Api-Key and estabelecimentoId) for authorization.

Troubleshooting

  • Common issues:

    • Invalid or missing API key or establishment ID will cause authentication errors.
    • Incorrect date formats for Data Inicio or Data Fim may result in API errors or empty responses.
    • Pagination parameters (Page, Page Size) set incorrectly might lead to unexpected result counts or no data.
    • Network connectivity issues can cause request failures.

  • Error messages:

    • "Operation ... not found": Indicates the specified operation name is invalid; ensure you select the correct operation.
    • API error responses will be passed through; check the message for details such as unauthorized access or invalid parameters.

  • Resolution tips:

    • Verify API credentials are correctly set in n8n.
    • Confirm date strings follow the expected format (usually ISO 8601).
    • Use sensible pagination values (e.g., start at page 0 or 1, reasonable page sizes).
    • Enable "Continue On Fail" if you want the workflow to proceed despite individual request errors.

Links and References

Discussion