Intelup icon

Intelup

Interact with the Intelup API

Actions335

legacy → Put Legacy Int Paradas By Id

AI-generated

Summary

Updates an existing legacy "paradas" (stop/downtime) record in the Intelup API by ID, sending a JSON body with the new field values via an HTTP PUT request.

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.
  • id (required) — ID of the legacy parada record to update. It is URL-encoded and substituted into the request path.
  • body__putPublicLegacyIntParadasById (required) — JSON request body. The 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. Invalid JSON raises a 'Body must be valid JSON' error.

Output shape

One output item per input item. Each item's json is the parsed response body from the Intelup API for the PUT call.

The response schema is not defined in the node, so the fields depend on the API. Requests authenticate with the fenixApi credential (token, code and unit-code headers) against the credential's base URL. If 'Continue on Fail' is enabled, a failed item returns { error: message } instead of stopping the workflow. The id and body are evaluated per input item.

Examples

Example 1: Mark a stop record as approved and give it an end date.

Version 3.42.3; Id set to the parada ID; Body JSON with par_datafim and par_dtaprovado filled in and other fields set as needed.

Example 2: Update many stop records from a spreadsheet.

Feed rows into the node; set Id to an expression like {{$json.id}} and the Body to an expression that builds the JSON from the row fields.

Links

Discussion