TrinksInstall

Overview

This node integrates with the Trinks API to manage client phone records. Specifically, the DELETE /v1/clientes/{clienteId}/telefones/{telefoneId} operation deletes a phone number associated with a particular client.

Common scenarios for this node include:

• Removing outdated or incorrect phone numbers from a client's profile.
• Cleaning up client contact information in bulk workflows.
• Automating client data maintenance by deleting specific phone entries based on business rules.

For example, if a client changes their phone number, you can use this node to delete the old phone record automatically.

Properties

Output

The node outputs JSON data representing the response from the Trinks API after attempting to delete the specified phone number. This typically includes confirmation of deletion or error details if the operation failed.

The output structure is:

{
  "json": {
    // API response fields confirming deletion or error message
  },
  "pairedItem": {
    "item": <index_of_input_item>
  }
}

No binary data 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 with appropriate headers including the API key and establishment ID.
• The node depends on the @devlikeapro/n8n-openapi-node package and custom parsers bundled within the node implementation.

Troubleshooting

• Operation Not Found Error: If the specified operation string does not match any available operations, the node will throw an error listing valid operations. Ensure the operation name is correct and matches exactly.
• Authentication Errors: Missing or invalid API key or establishment ID credentials will cause authentication failures. Verify that credentials are correctly set up in n8n.
• Invalid IDs: Providing non-numeric or incorrect Cliente Id or Telefone Id values may result in API errors. Confirm these IDs exist and are valid.
• Network Issues: Connectivity problems to the Trinks API endpoint will cause request failures. Check network access and proxy settings if applicable.
• Continue On Fail: If enabled, the node will return error details in the output JSON instead of stopping execution on failure, allowing workflows to handle errors gracefully.

Links and References

• Trinks API Documentation (official API docs for reference)
• n8n Documentation (for general node usage and credential setup)