TrinksInstall

Overview

This node integrates with the Trinks API to retrieve phone numbers associated with a specific client. It is designed to fetch all telephone records for a given client ID, which can be useful in scenarios such as customer management, contact verification, or syncing client contact details into other systems.

A practical example would be using this node to pull all phone numbers of a client before sending SMS notifications or updating a CRM system with the latest contact information.

Properties

Output

The node outputs JSON data representing the response from the Trinks API endpoint that lists phone numbers for the specified client. The structure typically includes an array or object containing phone number details such as type, number, and possibly metadata related to each phone entry.

No binary data output is produced by this operation.

Example output JSON (simplified):

{
  "telefones": [
    {
      "tipo": "celular",
      "numero": "+5511999999999"
    },
    {
      "tipo": "residencial",
      "numero": "+551133333333"
    }
  ]
}

Dependencies

• Requires an API key credential and an establishment ID credential configured in n8n to authenticate requests against 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 helper.

Troubleshooting

• Common issues:

  • Invalid or missing API key or establishment ID will cause authentication failures.
  • Providing an invalid or non-existent Cliente Id may result in empty responses or errors from the API.
  • Network connectivity issues can prevent successful API calls.

• Error messages:

  • "Operation ... not found": This indicates the requested operation is not defined in the node’s configuration. Ensure the correct resource and operation are selected.
  • API error messages returned in the JSON response will be passed through; check the message for clues (e.g., unauthorized, not found).

• Resolution tips:

  • Verify credentials are correctly set up and valid.
  • Confirm the Cliente Id exists in the Trinks system.
  • Check network access and proxy settings if applicable.
  • Enable "Continue On Fail" in the node settings to handle errors gracefully during batch processing.

Links and References

• Trinks API Documentation (official API docs for detailed endpoint info)
• n8n HTTP Request Node documentation for understanding request handling: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/