Intelup icon

Intelup

Interact with the Intelup API

Actions335

legacy → Post Legacy Int Paradas

AI-generated

Summary

Sends a POST request to the Intelup (Fenix) legacy integration endpoint for "paradas" (stoppage/downtime records) using a JSON body you supply, and returns the API's response for each input item.

Inputs

  • version — Intelup API version snapshot to use (3.42.3, 3.41.6, or 3.41.5). Defaults to 3.42.3.
  • body__postPublicLegacyIntParadas (required) — JSON request body. The Swagger-generated template lists fields such as plt_codigo_ext, mot_codigo, moe_codigo, res_codigo, cau_codigo, sol_codigo, eqp_codigo, par_dataini, par_datafim, par_tipo, par_tipo_parada, status_integracao, status_observacao, par_dtaprovado, pk_emp_codemp, pk_par_dataini, pk_par_horaini, pk_moe_codigo, inserted and updated. The placeholder values ('The task details') must be replaced with real data. Must be valid JSON or the node throws 'Body must be valid JSON'.

Output shape

One output item per input item, whose json is the parsed API response body.

The exact request path and HTTP method come from a bundled version catalog not shown in the source, so they are not documented here. Authentication uses the fenixApi credential (token, code and unit-code headers sent to the credential's base URL). The body is parsed once per input item, so expressions can vary it per item. With Continue On Fail enabled, failed items return {error: message} instead of stopping the workflow.

Examples

Example 1: Push a machine stoppage record from an upstream system into Intelup

Version 3.42.3; Body JSON with eqp_codigo, mot_codigo, par_dataini, par_datafim, par_tipo_parada and pk_* keys filled in, using expressions from previous node data.

Links

Discussion