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, specifically allowing users to retrieve a paginated list of professionals ("Profissionais") via the GET /v1/profissionais operation. It is useful in scenarios where you want to automate fetching professional data from the Trinks platform, such as syncing professional lists into CRMs, dashboards, or other systems.
Practical examples include:
- Automatically retrieving updated lists of professionals for scheduling or reporting.
- Integrating professional data into marketing or communication workflows.
- Building custom views or analytics based on professional information stored in Trinks.
Properties
| Name | Meaning |
|---|---|
| Page | The page number of results to retrieve (pagination). |
| Page Size | The number of items per page to retrieve (pagination). |
These properties are sent as query parameters in the API request to control pagination of the professionals list.
Output
The node outputs an array of JSON objects representing the response from the Trinks API for the professionals list. Each item corresponds to one professional's data as returned by the API.
The output structure is:
{
"json": {
// Full JSON response from GET /v1/profissionais endpoint
},
"pairedItem": {
"item": <index_of_input_item>
}
}
No binary data is produced by this node.
Dependencies
- Requires an API key credential and an establishment ID credential to authenticate requests to the Trinks API.
- The base URL used is
https://api.trinks.com. - The node sets headers including
Accept: application/json,Content-Type: application/json,X-Api-Key, andestabelecimentoIdfor authentication.
Troubleshooting
Common issues:
- Invalid or missing API key or establishment ID will cause authentication failures.
- Providing invalid pagination values (e.g., negative numbers) may result in API errors or empty responses.
- Network connectivity issues can prevent successful API calls.
Error messages:
- If the specified operation is not found, the node throws an error listing available operations.
- API errors from Trinks will be returned in the node output if "Continue On Fail" is enabled; otherwise, they will stop execution.
Resolutions:
- Ensure valid credentials are configured in n8n.
- Validate input parameters before running the node.
- Check network access to
api.trinks.com.
Links and References
- Trinks API Documentation (Assumed official docs URL, replace with actual if known)