TrinksInstall

Overview

This node integrates with the Trinks API to retrieve detailed information about a specific phone number associated with a client. It is designed to fetch data for a given client ID and phone ID, making it useful in scenarios where you need to access or verify contact details stored in the Trinks system.

Practical examples include:

• Retrieving a client's phone number details before sending notifications.
• Validating phone numbers linked to clients during customer support workflows.
• Synchronizing client phone data between Trinks and other systems.

Properties

Output

The node outputs a JSON object containing the response from the Trinks API for the requested phone record. This JSON includes all available details about the phone number associated with the specified client, such as the phone type, number, status, and any other metadata provided by the API.

No binary data output is produced by this node.

Example output structure (simplified):

{
  "id": 123,
  "clienteId": 456,
  "numero": "+5511999999999",
  "tipo": "mobile",
  "status": "active",
  ...
}

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.
• No additional external dependencies beyond the Trinks API and n8n's HTTP request capabilities.

Troubleshooting

• Operation Not Found Error: If the operation name does not match any available operations, the node will throw an error listing valid operations. Ensure that the operation string exactly matches "GET /v1/clientes/{clienteId}/telefones/{id}".
• 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 IDs: Providing non-numeric or incorrect client or phone IDs may result in API errors or empty responses. Confirm that IDs are valid and exist in the Trinks system.
• Network Issues: Connectivity problems to https://api.trinks.com can cause request failures. Check network settings and firewall rules if requests time out or fail.

Links and References

• Trinks API Documentation (for detailed API endpoints and data structures)
• n8n HTTP Request Node Documentation (for understanding how HTTP requests are handled within n8n)