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") indicating that the client did not show up ("clientefaltou"). It is useful in scenarios where businesses need to programmatically mark appointments as missed by clients, enabling automated follow-ups, reporting, or workflow adjustments based on client attendance.

For example, a salon using n8n could automatically update the status of no-show appointments after a scheduled time passes, triggering notifications or rescheduling workflows.

Properties

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

Output

The node outputs JSON data representing the response from the Trinks API after attempting to update the appointment status. This typically includes confirmation of the status change or details about the updated appointment.

If an error occurs and the node is configured to continue on failure, the output JSON will contain an error field with the error message.

No binary data output is produced by this node.

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 Trinks API endpoint:
PATCH https://api.trinks.com/v1/agendamentos/{agendamentoId}/status/clientefaltou
Proper configuration of credentials in n8n is necessary for successful API communication.

Troubleshooting

Common issues:
- Invalid or missing Agendamento Id can cause the API to reject the request.
- 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 the specified operation name does not match any available operations; ensure the correct operation string is used.
- API errors returned from Trinks (e.g., 4xx or 5xx HTTP status codes) will be included in the node output if "continue on fail" is enabled.
Resolutions:
- Verify that the Agendamento Id is correct and corresponds to an existing appointment.
- Check and update API credentials in n8n settings.
- Ensure network access to https://api.trinks.com.
- Use the node’s "continue on fail" option to handle errors gracefully in workflows.

Links and References

Trinks API Documentation (general reference for API endpoints and authentication)
n8n Documentation on HTTP Request Node (for understanding underlying HTTP calls)

TrinksInstall