Trinks

Nó N8N para interagir com a API do Trinks

Actions46

Agendamentos Actions
Clientes Actions
Clientes Creditos Actions
- POST /v1/clientes/{clienteId}/creditos
Clientes Etiquetas Actions
Clientes Telefones Actions
Clientes Vales Presentes Actions
- POST /v1/clientes/{clienteId}/valespresentes
Clube De Assinaturas Actions
Estabelecimentos Actions
- GET /v1/estabelecimentos
Etiquetas Actions
Fidelidade Actions
- GET /v1/fidelidade
Financeiro Formas Pagamento Actions
- GET /v1/formaspagamentos
Financeiro Motivos Descontos Actions
- GET /v1/motivosdescontos
Financeiro Transacoes Actions
- GET /v1/transacoes
Financeiro Vendas De Produto Actions
- GET /v1/vendas
Produtos Actions
- GET /v1/produtos
Profissionais Actions
Servicos Actions
- GET /v1/servicos
- GET /v1/servicos/{id}/promocoes

Overview

This node integrates with the Trinks API to create new "Etiquetas" (tags or labels) by sending a POST request to the /v1/etiquetas endpoint. It is useful for automating the creation of tags within the Trinks system, which can be used for categorization, filtering, or labeling entities such as appointments, customers, or services.

Practical examples include:

Automatically generating tags based on customer behavior or preferences.
Creating color-coded labels for different service types.
Adding descriptive tags to organize data in the Trinks platform.

Properties

Name	Meaning
Tipo Id	Numeric identifier representing the type of the tag to be created.
Conteudo	The textual content or label of the tag.
Cor	The color associated with the tag, typically used for visual identification.

Output

The node outputs JSON data representing the response from the Trinks API after creating the etiqueta. This JSON typically contains details about the newly created tag, such as its ID, type, content, and color.

No binary data output is produced by this node.

Example output structure (simplified):

{
  "id": "string",
  "tipoId": 0,
  "conteudo": "string",
  "cor": "string"
}

Dependencies

Requires an API key credential and an establishment ID credential to authenticate requests to the Trinks API.
The node sends HTTP requests to https://api.trinks.com.
Proper configuration of these credentials in n8n is necessary for successful operation.

Troubleshooting

Common issues:
- Missing or invalid API key or establishment ID will cause authentication failures.
- Providing invalid or missing required properties (tipoId, conteudo, or cor) may result in API errors.
- Network connectivity problems can prevent the node from reaching the Trinks API.
Error messages:
- "Operation POST /v1/etiquetas not found": Indicates the specified operation is not recognized; ensure the correct operation name is used.
- API error responses will be passed through in the output JSON under an error field if "Continue On Fail" is enabled.
Resolutions:
- Verify that API credentials are correctly set up in n8n.
- Ensure all required input properties have valid values.
- Check network connectivity and API availability.

Links and References

Trinks API Documentation (general reference for API endpoints and usage)
n8n documentation on HTTP Request Node for understanding how API calls are made within nodes

TrinksInstall