TrinksInstall

Overview

This node integrates with the Trinks API to retrieve service information related to a specific professional. The particular operation GET /v1/profissionais/{profissionalId}/servicos fetches a paginated list of services offered by a professional identified by their ID.

Common scenarios for this node include:

• Fetching all services provided by a given professional in a scheduling or booking workflow.
• Displaying available services dynamically based on the selected professional in an automation.
• Synchronizing service data from Trinks into another system or database.

For example, you might use this node to get all services for a hairstylist (professional) and then present those services as options in a customer booking form.

Properties

Output

The node outputs JSON data representing the response from the Trinks API for the requested professional's services. This typically includes an array of service objects with details such as service name, description, price, duration, and other relevant metadata.

The output structure is:

{
  "json": {
    // API response object containing the list of services and pagination info
  },
  "pairedItem": {
    "item": <index_of_input_item>
  }
}

No binary data output is produced by this node.

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 request headers include Accept: application/json, Content-Type: application/json, the API key, and the establishment ID.

Troubleshooting

• Operation Not Found Error: If the specified operation is not recognized, the node will throw an error listing available operations. Ensure that the operation string exactly matches one of the supported operations.
• Authentication Errors: Missing or invalid API key or establishment ID credentials will cause authentication failures. Verify that these credentials are correctly set up in n8n.
• Invalid Professional Id: Providing a non-existent or incorrect professional ID may result in empty responses or errors from the API.
• Pagination Issues: If page or pageSize parameters are set incorrectly (e.g., negative numbers), the API may return errors or unexpected results. Use valid positive integers.
• Network or API Downtime: Network issues or Trinks API downtime can cause request failures. Check connectivity and API status if errors persist.

Links and References

• Trinks API Documentation (general reference for API endpoints and usage)
• n8n HTTP Request Node Documentation (for understanding how HTTP requests work in n8n)

This summary is based solely on static analysis of the provided source code and property definitions.