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 interacts with the Trinks API, specifically allowing users to retrieve detailed information about a single appointment (agendamento) by its unique identifier. It is useful in scenarios where you need to fetch and process data for a specific booking or appointment within an automation workflow, such as confirming appointment details, updating records, or triggering follow-up actions based on the appointment data.
For example, you might use this node to:
- Retrieve appointment details before sending a reminder email.
- Fetch booking information to update a CRM system.
- Validate appointment status before allowing further processing.
Properties
| Name | Meaning |
|---|---|
| Id | The unique numeric identifier of the appointment to retrieve. This is a required field. |
Output
The node outputs a JSON object representing the appointment data retrieved from the Trinks API. The structure corresponds directly to the API response for the GET /v1/agendamentos/{id} endpoint, typically including fields such as appointment date, time, client details, service information, and status.
If the request fails and "Continue On Fail" is enabled, the output will contain an error object with a message describing the failure.
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 requests to
https://api.trinks.comwith appropriate headers including the API key and establishment ID. - Proper configuration of these credentials in n8n is necessary for successful execution.
Troubleshooting
Common issues:
- Invalid or missing API key or establishment ID will cause authentication failures.
- Providing an invalid or non-existent appointment Id will result in an error from the API.
- Network connectivity issues can prevent the node from reaching the Trinks API.
Error messages:
"Operation ... not found": Indicates that the specified operation is not recognized; ensure the correct operation name is selected.- API errors returned in the JSON response will be passed through; check the error message for details.
Resolutions:
- Verify that the API key and establishment ID credentials are correctly set up and valid.
- Confirm that the appointment Id exists and is correctly typed as a number.
- Enable "Continue On Fail" if you want the workflow to proceed despite individual item errors.
Links and References
- Trinks API Documentation (for detailed API endpoint specifications)
- n8n documentation on HTTP Request Node for understanding how API calls are made within nodes