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 information about professionals associated with a specific service category at an establishment. It is particularly useful for workflows that need to fetch lists of professionals filtered by service categories, such as scheduling systems, appointment booking automation, or staff management tools.
For example, you can use this node to get all professionals who provide a certain type of service (e.g., hairdressing, massage) at a particular establishment, optionally paginating through results.
Properties
| Name | Meaning |
|---|---|
| Servico Categoria Estabelecimento Id | The unique identifier of the service category within the establishment. This is required and used to specify which category's professionals to retrieve. |
| Page | The page number of results to retrieve, supporting pagination. Defaults to 0 (first page). |
| Page Size | The number of items per page to return, controlling the size of each paginated response. |
Output
The node outputs JSON data representing the response from the Trinks API endpoint for professionals filtered by the specified service category ID. The structure corresponds directly to the API's response schema, typically including details about each professional such as their identifiers, names, specialties, availability, and other relevant metadata.
If the API supports binary data in responses (not evident here), it would be included accordingly, but based on the code and operation, output is purely JSON.
Dependencies
- Requires an API key credential and an establishment ID credential to authenticate requests to the Trinks API.
- The base URL for the API is
https://api.trinks.com. - The node sets HTTP headers including
Accept: application/json,Content-Type: application/json, and custom headers for API key and establishment ID. - Pagination parameters (
pageandpageSize) are sent as query parameters.
Troubleshooting
- Operation Not Found Error: If the specified operation is not recognized, the node logs available operations and throws an error indicating the requested operation is invalid. Ensure the operation name matches exactly
"GET /v1/profissionais/{servicoCategoriaEstabelecimentoId}". - Missing or Invalid Credentials: Requests require valid API key and establishment ID credentials. Errors related to authentication will occur if these are missing or incorrect.
- Invalid or Missing Required Parameters: The
Servico Categoria Estabelecimento Idis mandatory. Omitting it or providing an invalid value may cause request failures. - Pagination Issues: Providing invalid values for
pageorpageSizecould result in unexpected responses or errors from the API. - API Request Failures: Network issues or API downtime will cause request errors. The node supports continuing on failure if enabled, returning error messages in the output JSON.
Links and References
- Trinks API Documentation (Assumed official docs for further details on endpoints and data structures)
- n8n Documentation on Creating Custom Nodes