Actions120
- Authentication Actions
- Bloqueios Actions
- Get Motivos
- Get Bloqueio Faturamento
- Get Bloqueio Conta
- Get Bloqueio Carteira
- Get Bloqueio Compra Pedido
- Get Bloqueio Cotacao Compra
- Get Bloqueio Data Minima Vencimento
- Get Bloqueio Estoque Negativo
- Get Bloqueio Financiamento Pedido
- Get Bloqueio Frete Pago
- Get Bloqueio Limite Credito
- Get Bloqueio Limite Individual
- Get Bloqueio Manutencao Preventiva
- Get Bloqueio Margem
- Get Bloqueio Mes Reajuste
- Get Bloqueio Parcela Minima
- Get Bloqueio Saldo Atrasado
- Desaprovar Bloqueio
- Liberar Bloqueio
- Liberar Bloqueio Limite Credito
- Liberar Bloqueio Limite Individual
- Classificacao Actions
- Cliente Actions
- Instituição Financeira Actions
- Linha de Crédito Actions
- Máquina Actions
- Mecânico Actions
- Motorista Actions
- Negócio Actions
- Nota Fiscal Actions
- Oficina Actions
- Orçamento Actions
- Orçamento Balcão Actions
- Ordem de Serviço Actions
- Criar Ordem de Serviço Completa
- Consultar por ID
- Consultar por Código Externo
- Listar Agendamentos
- Listar Agendamentos por ID
- Listar Status do Lock
- Listar Ordens de Serviço
- Incluir Ordem de Serviço
- Listar Ordens de Serviço Geral
- Incluir Apontamento
- Incluir Despesa
- Incluir Peça
- Incluir Serviço
- Editar Peça
- Editar Serviço
- Editar Veículo
- Incluir Observação
- Ordem Serviço Tipo Actions
- Pedido Actions
- Política de Prazo Actions
- Política de Preço Actions
- Produto Actions
- Prospect Actions
- Saída Actions
- Serviço Actions
- Status Financiamento Actions
- Título Actions
- Veículo Cliente Actions
- Veículo Próprio Actions
- Vendas Actions
- Vendedor Actions
Veículo Cliente → Get por Cliente
AI-generatedOverview
This node integrates with the Nuvem Solution API to perform various operations across multiple resources. Specifically, for the Veículo Cliente resource and the Get por Cliente operation, it retrieves a list of vehicles associated with a given customer ID.
This functionality is useful in scenarios where you need to fetch all vehicles registered under a particular customer, such as in fleet management, vehicle servicing, or customer relationship management systems. For example, a workshop system could use this to display all vehicles owned by a customer when creating a service order.
Properties
| Name | Meaning |
|---|---|
| Cliente ID | The unique identifier (ID) of the customer whose vehicles are to be retrieved. This is a required string input. |
Output
The node outputs JSON data representing the vehicles associated with the specified customer. The structure corresponds to the response from the endpoint:
GET /erp/oficina/veiculosClientes/porCliente/{clienteId}
The output JSON typically includes an array of vehicle objects with details such as vehicle identifiers, model, chassis number, registration data, and other relevant vehicle information linked to the customer.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Nuvem Solution API.
- The node uses the base URL and authentication tokens obtained via these credentials.
- Proper configuration of the API credentials within n8n is necessary for successful requests.
Troubleshooting
- Authentication errors: If the node fails due to authentication issues, verify that the API key credential is correctly configured and valid.
- Invalid Cliente ID: Ensure the provided Cliente ID exists in the system; otherwise, the API may return an error or empty results.
- API endpoint changes: If the API endpoint changes or is deprecated, the node will fail. Confirm the API version compatibility.
- Network issues: Connectivity problems between n8n and the Nuvem Solution API can cause request failures.
Common error messages include:
"Authentication failed: Invalid response from server"— Check API credentials."The operation "getPorCliente" is not supported!"— Ensure the correct operation name is used.- HTTP 404 or 400 errors — Verify the Cliente ID and parameters.
Links and References
- Nuvem Solution API Documentation (generic link, replace with actual if available)
- n8n documentation on Creating Custom Nodes
- REST API best practices for troubleshooting HTTP errors
Note: This summary is based solely on static analysis of the provided source code and property definitions without runtime execution.