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 retrieve scheduling information for professionals on a specified date. It is particularly useful in scenarios where you need to fetch available appointment slots, check professional schedules, or manage bookings programmatically within an automation workflow.
For example, a salon management system could use this node to automatically pull daily availability of stylists and update a booking calendar or notify clients about open slots.
Properties
| Name | Meaning |
|---|---|
| Data | The target date for which to retrieve professional schedules (string format, e.g., "2024-06-01"). |
| Intervalos | Number of intervals to consider in the query (number). |
| Servico Id | Identifier of the service related to the schedule (number). |
| Servico Duracao | Duration of the service in minutes (number). |
| Profissional Id | Identifier of the professional whose schedule is being queried (number). |
| Page | Pagination page number for results (number). |
| Excluir Excecoes De Agendamento Online | Boolean flag to exclude online scheduling exceptions from the results (true/false). |
Output
The node outputs JSON data representing the response from the Trinks API endpoint /v1/agendamentos/profissionais/{data}. This typically includes scheduling details such as available time slots, booked appointments, and possibly metadata about the professional or service.
If the API returns binary data (not indicated here), it would be summarized accordingly, but based on the code and operation, output is JSON only.
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.com. - Proper configuration of these credentials in n8n is necessary for successful execution.
Troubleshooting
Common Issues:
- Missing or invalid API key or establishment ID will cause authentication failures.
- Incorrect date format in the "Data" property may lead to API errors or empty responses.
- Providing invalid IDs (service or professional) might result in no data or error messages.
- Pagination parameters must be handled carefully to avoid missing data.
Error Messages:
"Operation ... not found": Indicates that the specified operation name does not match any defined operations. Verify the operation string.- Network or authentication errors: Check API key and establishment ID validity.
- If the node throws errors related to request construction, ensure all required properties are set correctly.
Links and References
- Trinks API Documentation (general reference; actual docs URL may vary)
- n8n HTTP Request Node documentation for understanding request options: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/
This summary is based solely on static analysis of the provided source code and property definitions.