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 "in attendance" (status "ematendimento"). It is useful in scenarios where you want to programmatically mark an appointment as currently being attended, for example, in a salon or clinic management workflow. By automating this status update, businesses can keep their scheduling system synchronized with real-time service progress.

Practical example: When a client arrives and the service starts, this node can be triggered to update the appointment status automatically, ensuring all team members and systems reflect the current state.

Properties

Name	Meaning
Agendamento Id	The unique numeric identifier of the appointment to update. This specifies which appointment's status will be changed to "in attendance".

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, confirmation of the status change, and any related metadata returned by the API.

No binary data output is produced by this operation.

Dependencies

Requires an API key credential and an establishment ID credential to authenticate requests to the Trinks API.
The node sends HTTP PATCH requests to the endpoint https://api.trinks.com/v1/agendamentos/{agendamentoId}/status/ematendimento.
Proper configuration of these credentials within n8n is necessary for successful execution.

Troubleshooting

Common issues:
- Invalid or missing Agendamento Id will cause the API request to fail.
- Incorrect or expired API key or establishment ID credentials will result in authentication errors.
- Network connectivity problems may prevent reaching the Trinks API endpoint.
Error messages:
- "Operation ... not found": Indicates that the specified operation name does not match any available operations; ensure the correct operation string is used.
- API error responses (e.g., 401 Unauthorized, 404 Not Found) usually indicate credential issues or invalid appointment IDs.
Resolutions:
- Verify that the Agendamento Id is correct and corresponds to an existing appointment.
- Check that API credentials are correctly set up and have sufficient permissions.
- Ensure network access to https://api.trinks.com is allowed from your environment.

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 n8n workflows

TrinksInstall