IntelupInstall

Summary

Creates a maintenance service order item in Intelup by sending a user-supplied JSON body to the Intelup public maintenance service-order-item endpoint (POST) and returns the API response.

Inputs

• version — Intelup API version snapshot to use: 3.42.3 (default), 3.41.6, or 3.41.5. Selects which operation definition is used.
• body__postPublicMaintenanceServiceOrderItem (required) — JSON request body describing the item. The prefilled template includes fields such as data_inicio, data_inicio_real, data_fim, data_fim_real, data_criacao, detalhes, status_exec, status_lub_exec, status_lub, status_qtd, status_qualitativa, id_service_order, id_servico, grupo_usuario, executante, elemento, equipamento, id_item_rota, valor_minimo, valor_maximo, codigo, and parado. Dates use YYYY-MM-DDTHH:mm:ssZ format. Replace the placeholder values. Must be valid JSON or the node throws 'Body must be valid JSON'.

Output shape

One output item per input item, with the Intelup API's JSON response in the item's json field.

The request runs once per input item, authenticated with the fenixApi credential (token, code and unit-code headers sent to the credential's base URL). The endpoint path is not visible in the supplied source because it comes from a generated version catalog. With Continue On Fail enabled, a failed item returns {error: message} instead of stopping the workflow.

Examples

Example 1: Add a lubrication check item to an existing service order.

Version 3.42.3; Body JSON with id_service_order, id_servico, equipamento, codigo, status_lub_exec and detalhes filled in.

Example 2: Create items for many rows from a spreadsheet.

Feed rows into the node and set the body to an expression such as {{ JSON.stringify($json) }} so each item posts its own body.

Links

• n8n community nodes installation guide