Trinks icon

Trinks

Nó N8N para interagir com a API do Trinks
Join our community

Actions46

Overview

This node integrates with the Trinks API to create a new phone number entry for a specific client. It is designed to send a POST request to the endpoint /v1/clientes/{clienteId}/telefones, adding telephone details such as area code, number, type, and country code to a client's profile.

Common scenarios where this node is useful include:

  • Automating customer data management by programmatically adding phone numbers to client records.
  • Synchronizing contact information from other systems into Trinks.
  • Bulk updating or enriching client profiles with multiple phone contacts.

For example, you could use this node in a workflow that processes new customer signups and automatically adds their phone numbers to the Trinks system.

Properties

Name Meaning
Cliente Id The unique identifier of the client to whom the phone number will be added.
Ddd The area code (local dialing code) of the phone number.
Numero The actual phone number digits.
Tipo Id The type identifier of the phone number (e.g., mobile, landline).
Ddi The international dialing code (country code) of the phone number.

Output

The node outputs JSON data representing the response from the Trinks API after creating the phone number. This typically includes confirmation details of the newly created phone record, such as its ID and stored values.

If an error occurs, the output JSON will contain an error field with the error message.

The node does not output binary data.

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.
  • The request headers include Accept: application/json, Content-Type: application/json, the API key, and the establishment ID.

Troubleshooting

  • Operation Not Found Error: If the specified operation is incorrect or missing, the node logs available operations and throws an error indicating the operation was not found. Ensure the operation name matches exactly "POST /v1/clientes/{clienteId}/telefones".
  • 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 Input Data: Providing invalid or incomplete phone number details (e.g., empty numero or invalid tipoId) may result in API errors. Validate input properties before execution.
  • Network Issues: Connectivity problems to api.trinks.com will cause request failures. Check network access and proxy settings if applicable.

Links and References

Discussion