Actions46
- Agendamentos Actions
- GET /v1/agendamentos
- POST /v1/agendamentos
- GET /v1/agendamentos/{id}
- PUT /v1/agendamentos/{agendamentoId}
- PATCH /v1/agendamentos/{agendamentoId}/status/confirmado
- PATCH /v1/agendamentos/{agendamentoId}/status/cancelado
- PATCH /v1/agendamentos/{agendamentoId}/status/finalizado
- PATCH /v1/agendamentos/{agendamentoId}/status/clientefaltou
- PATCH /v1/agendamentos/{agendamentoId}/status/ematendimento
- GET /v1/agendamentos/profissionais/{data}
- Clientes Actions
- Clientes Creditos Actions
- Clientes Etiquetas Actions
- Clientes Telefones Actions
- Clientes Vales Presentes Actions
- Clube De Assinaturas Actions
- Estabelecimentos Actions
- Etiquetas Actions
- Fidelidade Actions
- Financeiro Formas Pagamento Actions
- Financeiro Motivos Descontos Actions
- Financeiro Transacoes Actions
- Financeiro Vendas De Produto Actions
- Produtos Actions
- Profissionais Actions
- Servicos Actions
Overview
This node integrates with the Trinks API to update the status of a specific appointment (Agendamento) to "finalizado" (finished). It is designed to send a PATCH request to the endpoint /v1/agendamentos/{agendamentoId}/status/finalizado, marking an appointment as completed.
Common scenarios include:
- Automating appointment workflows by programmatically updating their status once services are rendered.
- Synchronizing appointment statuses between Trinks and other systems.
- Triggering downstream processes or notifications after an appointment is finalized.
Example use case:
- After a customer’s service is completed, this node can be used in an n8n workflow to mark the appointment as finished in Trinks automatically.
Properties
| Name | Meaning |
|---|---|
| Agendamento Id | The unique numeric identifier of the appointment to update. |
Output
The node outputs the JSON response returned by the Trinks API after the PATCH request. This typically includes details about the updated appointment status or confirmation of the successful update.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the Trinks API.
- Needs the establishment ID credential value to be included in request headers.
- The node sends HTTP requests to
https://api.trinks.com.
Troubleshooting
- Error: Operation not found — This occurs if the specified operation string does not match any available operations. Ensure the operation name is exactly
"PATCH /v1/agendamentos/{agendamentoId}/status/finalizado". - Authentication errors — If the API key or establishment ID credentials are missing or invalid, the request will fail. Verify that valid credentials are configured.
- Invalid Agendamento Id — Providing a non-existent or incorrect appointment ID will cause the API to return an error. Confirm the ID is correct and exists in Trinks.
- Network or API errors — Check network connectivity and Trinks API status if requests time out or fail unexpectedly.
Links and References
- Trinks API Documentation (general reference for API endpoints and authentication)
- n8n HTTP Request Node documentation for understanding how HTTP methods and headers work within n8n workflows