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 manage "Clientes" (clients/customers). Specifically, the DELETE operation for /v1/clientes/{clienteId} allows users to delete a client by their unique identifier. This is useful in scenarios where you need to remove outdated or incorrect client records from your system automatically as part of a workflow.
Practical examples include:
- Automatically deleting clients who have unsubscribed or requested data removal.
- Cleaning up test or duplicate client entries after data import.
- Integrating with other systems to synchronize client deletions.
Properties
| Name | Meaning |
|---|---|
| Cliente Id | The unique numeric ID of the client to delete |
Output
The node outputs a JSON object representing the response from the Trinks API after attempting to delete the specified client. Typically, this will contain confirmation of deletion or relevant status information returned by the API.
If an error occurs and the node is configured to continue on failure, the output JSON will contain an error field with the error message.
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 base URL for the API is
https://api.trinks.com. - The node sends HTTP requests with headers including
Accept: application/json,Content-Type: application/json,X-Api-Key, andestabelecimentoId.
Troubleshooting
- Operation Not Found Error: If the operation name is incorrect or not supported, the node throws an error listing available operations. Ensure the operation string matches exactly
"DELETE /v1/clientes/{clienteId}". - Authentication Errors: Missing or invalid API key or establishment ID credentials will cause authentication failures. Verify that valid credentials are set up in n8n.
- Invalid Cliente Id: Providing a non-existent or invalid client ID may result in API errors. Confirm the client ID exists before attempting deletion.
- Network Issues: Connectivity problems to
https://api.trinks.comwill cause request failures. Check network access and proxy settings if applicable.
Links and References
- Trinks API Documentation (general reference for API endpoints and authentication)
- n8n documentation on HTTP Request Node for understanding how API calls are made within workflows