Intelup icon

Intelup

Interact with the Intelup API

Actions335

maintenance → Post Maintenance Service Order

AI-generated

Summary

Creates a maintenance service order (ordem de serviço) in Intelup by sending a user-supplied JSON body to the Intelup public maintenance service-order endpoint, once per input item.

Inputs

  • version (required) — Intelup API version to target: 3.42.3 (default), 3.41.6 or 3.41.5. Selects which operation definition is used.
  • body__postPublicMaintenanceServiceOrder (required) — JSON body for the service order. The template includes fields such as serv_data_inicio/serv_data_fim (planned dates), serv_data_inicio_real/serv_data_fim_real (actual dates), serv_descri, serv_status (e.g. integratedMaintenance.initialStatus, inProgressStatus, waitingApprovalStatus, finishedStatus, approvedStatus, reprovedStatus), serv_solicitante, serv_executante, serv_turno, serv_codigo, integracao (0/1), aprovado (0/1), serv_aprovador, serv_data_aprovacao, observacao, and ID references like id_rota, id_item_os, id_status, id_service_order_type, id_atividade, id_prioridade, id_nota_manutencao, elemento, equipamento, grupo_usuario. Dates use ISO format. Must be valid JSON or the node errors with 'Body must be valid JSON'. Which fields the API actually requires isn't declared; the example values are placeholders to replace.

Output shape

One output item per input item, whose json is the Intelup API's response to the create request.

Requires the Intelup (fenixApi) credential, whose base URL, token, code and unit code are sent as headers. The HTTP method and path are looked up from a bundled version catalog (not visible in the source pack). If Continue On Fail is enabled, a failed item yields {error: message} instead of stopping the workflow. The body is parsed per item, so expressions can vary it between items.

Examples

Example 1: Open a new corrective service order for an equipment from an upstream trigger

Version 3.42.3; body with serv_descri, serv_status set to integratedMaintenance.initialStatus, equipamento, id_prioridade, serv_solicitante, and planned start/end dates, mapped via expressions.

Example 2: Push a completed order with approval details

Body with serv_status integratedMaintenance.approvedStatus, serv_data_inicio_real/serv_data_fim_real, aprovado 1, serv_aprovador, serv_data_aprovacao and observacao.

Links

Discussion