TrinksInstall

Overview

This node integrates with the Trinks API to update client information. Specifically, the PUT /v1/clientes/{clienteId} operation allows users to modify details of an existing client by specifying their unique client ID and providing updated data fields such as name, email, CPF (Brazilian individual taxpayer registry identification), gender, and other optional notes.

Common scenarios for this node include:

• Synchronizing client records between Trinks and another system.
• Updating client contact information or demographic data after receiving new inputs.
• Correcting or enriching client profiles in bulk workflows.

For example, a business could use this node to update the email address and gender of a client after they submit a profile update form on a website.

Properties

Output

The node outputs the JSON response returned by the Trinks API after updating the client. This typically includes the updated client object reflecting the changes made.

The output structure is:

{
  "json": {
    // Updated client data as returned by the API
  },
  "pairedItem": {
    "item": <index_of_input_item>
  }
}

No binary data is produced by this node.

Dependencies

• Requires an API key credential for authenticating requests to the Trinks API.
• Needs the establishment ID credential value to be included in request headers.
• The base URL for the API is https://api.trinks.com.
• The node expects JSON content type and uses standard HTTP methods.

Troubleshooting

• Operation Not Found Error: If the specified operation string does not match any available operations, the node throws an error listing valid operations. Ensure the operation name matches exactly.
• Authentication Errors: Missing or invalid API key or establishment ID will cause authentication failures. Verify credentials are correctly configured.
• Invalid Cliente Id: Providing a non-existent or incorrect client ID will result in API errors. Confirm the client ID exists before attempting updates.
• Empty Required Fields: The Cliente Id is mandatory; omitting it will cause the node to fail.
• Deprecated Field Warning: The Sexo field is obsolete and should be avoided; use Genero instead.

Links and References

• Trinks API Documentation (hypothetical link)
• n8n HTTP Request Node Documentation (for understanding underlying request mechanics)