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
Saída → Create Saida Completa
AI-generatedOverview
The "Create Saida Completa" operation in the Saída resource allows users to create a complete output record related to a service order or similar workflow. This operation sends detailed information about an output event, including vehicle, driver, mileage, dates, and reasons for the output, to the Nuvem Solution API.
This node is beneficial in scenarios where a comprehensive record of a service or delivery output must be created and tracked within an ERP or workshop management system. For example, it can be used to log the departure and return details of a service vehicle, including kilometers traveled and the reason for the trip, ensuring accurate operational tracking and reporting.
Practical examples:
- Logging a mechanic's complete service trip with start and end times, mileage, and vehicle/driver details.
- Recording the dispatch of a vehicle for a service order with all relevant metadata for billing or auditing purposes.
Properties
| Name | Meaning |
|---|---|
| ID do Pedido | The order ID associated with this output (required). |
| Filial ID | Branch ID where the output is registered (required). |
| Veículo Atendimento ID | ID of the service vehicle involved in the output (required). |
| Motorista ID | ID of the driver responsible for the output (required). |
| Saída de OS | Indicates if this output is related to a service order; options: Indefinido, Não, Sim (required). |
| Saída KM | Mileage at the time of departure (required). |
| Data de Saída | Date of departure (required). |
| Hora de Saída | Time of departure in HH:MM format. |
| Retorno KM | Mileage at the time of return (required). |
| Data de Retorno | Date of return (required). |
| Hora de Retorno | Time of return in HH:MM format. |
| KM Custo | Cost-related mileage (required). |
| Motivo | Reason for the output, up to 1200 characters. |
Output
The node outputs a JSON object representing the response from the Nuvem Solution API after creating the complete output record. This typically includes confirmation details such as IDs, status, timestamps, and any other data returned by the API regarding the created output.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the Nuvem Solution API.
- Requires credentials containing an API base URL, software key, secret, user ID, and user key for authentication.
- The node uses bearer token authentication obtained via these credentials.
- Proper configuration of the n8n credential for the Nuvem Solution API is necessary.
Troubleshooting
- Authentication failures: Ensure that the provided software key, secret, user ID, and user key are correct and have not expired.
- Missing required fields: All required properties (e.g., ID do Pedido, Filial ID, Veículo Atendimento ID, Motorista ID, Saída de OS, Saída KM, Data de Saída, Retorno KM, Data de Retorno, KM Custo) must be provided; otherwise, the API may reject the request.
- Invalid date/time formats: Dates should be in ISO 8601 format (dateTime), and times should follow the HH:MM format.
- API errors: If the API returns errors, check the error message for details. Common issues include invalid IDs, unauthorized access, or malformed requests.
- Network issues: Verify network connectivity to the API endpoint.
Links and References
- Nuvem Solution API Documentation (generic link, replace with actual docs if available)
- n8n documentation on HTTP Request Node for understanding API calls
- Best practices for API Authentication in n8n