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 update the status of a specific appointment (agendamento) to "confirmed". It is useful in scenarios where you want to programmatically confirm appointments within an automated workflow, such as after receiving payment confirmation or manual approval. For example, a salon booking system could use this node to automatically mark appointments as confirmed once a client completes a deposit.

Properties

Name	Meaning
Agendamento Id	The unique numeric identifier of the appointment to be updated to confirmed status.

Output

The node outputs JSON data representing the response from the Trinks API after updating the appointment status. This typically includes details about the updated appointment, such as its new status and any related metadata returned by the API.

No binary data output is produced by this operation.

Dependencies

Requires an API key credential for authenticating with the Trinks API.
Requires an establishment ID credential associated with the Trinks account.
The node sends HTTP PATCH requests to the endpoint https://api.trinks.com/v1/agendamentos/{agendamentoId}/status/confirmado.
Proper configuration of credentials in n8n is necessary for successful API communication.

Troubleshooting

Common issues:
- Invalid or missing API key or establishment ID will cause authentication failures.
- Providing an invalid or non-existent Agendamento Id will result in errors from the API indicating the resource was not found.
- Network connectivity problems can prevent the request from completing.
Error messages:
- "Operation ... not found": Indicates the specified operation string does not match any supported operations; ensure the correct operation name is used.
- API error responses will be passed through in the node's output if "Continue On Fail" is enabled, allowing inspection of error details.
Resolutions:
- Verify that the API key and establishment ID credentials are correctly set up in n8n.
- Confirm the Agendamento Id exists and is valid.
- Check network access to api.trinks.com.

Links and References

Trinks API Documentation (general reference, actual docs URL may vary)
n8n documentation on HTTP Request Node for understanding underlying request mechanics

TrinksInstall