Trinks

Interact with Trinks API
Join our community

Actions8

Overview

This node integrates with the Trinks API to manage appointments, specifically allowing users to cancel an existing appointment. The cancellation operation requires specifying the appointment to cancel, a reason for cancellation, and an identifier indicating who performed the cancellation.

Typical use cases include:

  • Automatically canceling appointments based on external triggers or conditions.
  • Allowing customer service workflows to update appointment statuses programmatically.
  • Integrating appointment cancellations into broader automation flows such as CRM updates or notifications.

For example, if a client calls to cancel their appointment, this node can be used in an n8n workflow to update the appointment status in Trinks with the cancellation reason and who canceled it.

Properties

Name Meaning
Appointment ID The unique identifier of the appointment to cancel.
Reason The reason for canceling the appointment.
Who Canceled (ID) Numeric identifier representing who canceled the appointment, as defined by the API.

Output

The node outputs JSON data representing the response from the Trinks API after attempting to cancel the appointment. This typically includes details about the updated appointment status and confirmation of the cancellation.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Trinks API.
  • The node uses HTTP PATCH requests to the endpoint /v1/agendamentos/{appointmentId}/status/cancelado to perform the cancellation.
  • Proper configuration of the API credentials in n8n is necessary for successful communication.

Troubleshooting

  • Common issues:

    • Invalid or missing Appointment ID will cause the API call to fail.
    • Providing an incorrect "Who Canceled" ID may result in unexpected behavior or errors depending on API validation.
    • Network or authentication errors if the API key is invalid or not configured properly.

  • Error messages:

    • Errors returned from the API will be propagated by the node, often indicating issues like "Appointment not found" or "Unauthorized".
    • To resolve, verify that the Appointment ID exists, the API key is valid, and the user has permission to cancel appointments.

Links and References

Discussion