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
Ordem de Serviço → Incluir Apontamento
AI-generatedOverview
The "Incluir Apontamento" operation under the "Ordem de Serviço" (Service Order) resource allows users to include or add an appointment (apontamento) to a service order in the Nuvem Solution system. This node operation sends a POST request with a JSON body containing the details of the appointment to be added.
This operation is beneficial in scenarios where service orders need to be updated dynamically with new appointments, such as scheduling mechanic tasks, recording work done, or tracking service progress within a workshop or maintenance environment.
Practical example:
A workshop manager uses this node to add a new appointment entry to an existing service order, specifying details like the date, time, mechanic assigned, and description of the task performed. This helps keep the service order up-to-date and facilitates better workflow management.
Properties
| Name | Meaning |
|---|---|
| Request Body | JSON body for the request. This should contain the appointment details to be included in the service order. The structure depends on the API's expected format for an appointment object. |
Output
- The output is a JSON array containing the response from the API after including the appointment.
- The response typically includes confirmation details about the newly created appointment, such as its ID, timestamps, status, or any other metadata returned by the API.
- There is no indication that binary data is returned by this operation.
Dependencies
- Requires an API key credential for authentication with the Nuvem Solution API.
- The node uses the base URL, software key, secret, user ID, and user key credentials to authenticate and authorize requests.
- The node makes HTTP POST requests to the endpoint
/erp/oficina/ordensServico/apontamentoon the configured base URL. - Proper configuration of the API credentials in n8n is necessary for successful execution.
Troubleshooting
- Invalid JSON in Request Body: If the JSON provided in the "Request Body" property is malformed, the API will likely return an error. Ensure the JSON is valid and matches the expected schema for an appointment.
- Authentication Errors: If the API credentials are incorrect or expired, authentication will fail. Verify that the API key and related credentials are correctly set up and have not expired.
- API Endpoint Errors: If the service order system is down or the endpoint changes, requests may fail. Check the API status and update the base URL if necessary.
- Missing Required Fields: The API might require certain fields in the appointment JSON. Omitting these can cause errors. Consult the API documentation for required fields.
- Permission Issues: The authenticated user must have permission to modify service orders. Lack of permissions will result in authorization errors.
Links and References
- Nuvem Solution API Documentation (general reference; specific endpoint docs should be consulted for detailed request body structure)
- For more information on service orders and appointments, refer to the "Oficina" or "Ordem de Serviço" sections in the official API docs.
Note: This summary is based solely on static analysis of the provided source code and input properties. Runtime behavior and dynamic responses depend on the actual API implementation and usage context.