Trinks

Interact with Trinks API
Join our community

Actions8

Overview

This node integrates with the Trinks API to manage appointments, customers, professionals, and services. Specifically, for the Appointment - Create operation, it allows users to schedule a new appointment by specifying the customer, professional, service, and start datetime.

Common scenarios where this node is beneficial include:

  • Automating appointment scheduling workflows in salons, clinics, or service businesses.
  • Integrating booking systems with other tools like CRMs or calendars.
  • Creating appointments programmatically based on user input or external triggers.

For example, you can use this node to create an appointment for a customer with a specific professional for a particular service at a chosen time, streamlining the booking process without manual entry into the Trinks platform.

Properties

Name Meaning
Customer ID The unique identifier of the customer for whom the appointment is being created.
Professional ID The unique identifier of the professional who will provide the service during the appointment.
Service ID The unique identifier of the service to be provided in the appointment.
Start Datetime The scheduled start date and time of the appointment in ISO 8601 format (dateTime).

Output

The output is a JSON object representing the newly created appointment as returned by the Trinks API. This typically includes details such as appointment ID, customer info, professional info, service details, start time, status, and any other metadata provided by the API.

No binary data output is produced by this operation.

Example output structure (simplified):

{
  "id": "appointment_id",
  "clienteId": "customer_id",
  "profissionalId": "professional_id",
  "servicoId": "service_id",
  "inicio": "2024-06-01T10:00:00Z",
  "status": "scheduled",
  ...
}

Dependencies

  • Requires an active connection to the Trinks API via an API key credential configured in n8n.
  • The node uses HTTP requests to interact with the Trinks REST endpoints.
  • Proper API authentication credentials must be set up in n8n before using this node.

Troubleshooting

  • Missing Required Fields: If any of the required properties (Customer ID, Professional ID, Service ID, Start Datetime) are missing or invalid, the API will likely return an error. Ensure all required fields are correctly filled.
  • Authentication Errors: If the API key credential is invalid or missing, the node will fail to authenticate. Verify that the API key is correct and has necessary permissions.
  • Invalid IDs: Using non-existent or incorrect IDs for customer, professional, or service will cause the API to reject the request. Confirm IDs exist in the Trinks system.
  • Date Format Issues: The Start Datetime must be in a valid ISO 8601 format. Incorrect formatting may lead to errors.
  • API Rate Limits or Downtime: Network issues or API rate limits might cause failures. Check API status and retry if needed.

Error messages from the node usually reflect the underlying API response; reading those messages carefully helps identify the root cause.

Links and References

Discussion