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 perform various operations on different resources. Specifically, for the "Etiquetas" resource and the "DELETE /v1/etiquetas/{etiquetaId}" operation, it deletes a tag (etiqueta) identified by its unique ID. This is useful in scenarios where you need to programmatically remove tags from your system, such as cleaning up outdated or incorrect labels.
Practical example: Automatically deleting tags that are no longer relevant after a certain event or time period, helping maintain an organized tagging system.
Properties
| Name | Meaning |
|---|---|
| Etiqueta Id | The unique numeric identifier of the tag (etiqueta) to delete |
Output
The node outputs the JSON response returned by the Trinks API after attempting to delete the specified etiqueta. This typically includes confirmation of deletion or error details if the operation failed.
If the API returns binary data (not typical for a DELETE operation), it would be included accordingly, but this operation primarily deals with JSON responses.
Dependencies
- Requires an API key credential and an establishment ID credential to authenticate requests to the Trinks API.
- The base URL for API requests is
https://api.trinks.com. - The node sends HTTP requests with headers including
Accept: application/json,Content-Type: application/json, and authentication headers.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Etiqueta Id will likely result in an error from the API indicating the tag was not found.
- Missing or incorrect API credentials will cause authentication failures.
- Network connectivity issues can prevent successful API calls.
Error messages:
"Operation ... not found": Indicates the specified operation string does not match any available operation; ensure the correct operation name is used.- API errors returned in the JSON response will be passed through; check the message for details.
Resolutions:
- Verify the Etiqueta Id is correct and exists in the system.
- Ensure API credentials are correctly configured and valid.
- Check network connectivity and endpoint accessibility.
Links and References
- Trinks API Documentation (for detailed API endpoints and usage)
- n8n documentation on HTTP Request Node for understanding how API calls are made within n8n nodes.