Trinks

Interact with Trinks API
Join our community

Actions8

Overview

This node integrates with the Trinks API to manage various resources such as customers, appointments, professionals, and services. Specifically for the Customer - Create operation, it allows users to create a new customer record in the Trinks system by providing essential details like the customer's name and optionally their email address.

Common scenarios where this node is beneficial include:

  • Automating customer onboarding workflows by creating customer profiles when new signups occur.
  • Synchronizing customer data from other systems into Trinks.
  • Building appointment booking systems that require customer records to be created dynamically.

For example, after collecting user information via a web form, you can use this node to create a corresponding customer in Trinks automatically.

Properties

Name Meaning
Name The full name of the customer to be created. This is a required field.
Email The email address of the customer. Optional but recommended for contact purposes.

Output

The output JSON contains the response from the Trinks API after creating the customer. It typically includes the newly created customer's details such as their unique identifier, name, email, and any other metadata returned by the API.

Example output structure (simplified):

{
  "id": "string",
  "nome": "Customer Name",
  "email": "customer@example.com",
  ...
}

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Trinks API.
  • An API key credential for authenticating requests to Trinks must be configured in n8n.
  • The node uses a helper function (trinksRequest) to make HTTP requests to the Trinks API endpoints.

Troubleshooting

  • Missing Required Fields: If the "Name" property is not provided, the node will throw an error because it is mandatory.
  • Authentication Errors: Ensure the API key credential is correctly set up and has sufficient permissions.
  • API Request Failures: Network issues or invalid parameters may cause the API call to fail. Check the error message for details.
  • Unexpected Response Format: If the API changes its response format, the node might not parse the output correctly.

To resolve errors:

  • Verify all required input properties are filled.
  • Confirm API credentials are valid and have access rights.
  • Review the error messages returned by the node for specific hints.

Links and References

Discussion