Intelup icon

Intelup

Interact with the Intelup API

Actions335

legacy → Put Legacy Int Expdadostpf By Id

AI-generated

Summary

Updates a legacy integration "expdadostpf" record (experiment/tag data entries) by ID through the Intelup API, sending the JSON body as a PUT request. The exact HTTP path comes from a generated catalog that isn't included in the source pack.

Inputs

  • version — API version snapshot to use: 3.42.3 (default), 3.41.6 or 3.41.5. Selects which operation definition is run.
  • id (required) — Identifier of the expdadostpf record to update. It is URL-encoded and substituted into the path.
  • body__putPublicLegacyIntExpdadostpfById (required) — JSON request body. The template lists fields such as plt_codigo, cli_codigo, tag_codigo, tag_codigo_ext, tag_descricao, exp_periodo_type, exp_data, exp_valor_str, exp_valor_str_subst, exp_tipoinput, exp_atrib, exp_dtatualiz, status_integracao, exp_statusconsist, exp_justificativa, exp_tipo, exp_aprovado, exp_disponibilizado and exp_dtaprovado. The placeholder values must be replaced. Invalid JSON throws 'Body must be valid JSON'.

Output shape

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

Each input item triggers its own PUT request. The credentials (base URL, token, code, unit code) are sent as headers. With Continue On Fail enabled, a failed item returns {error: message} instead of stopping the workflow. The response schema isn't defined in the source.

Examples

Example 1: Approve an existing record and add a justification

Version 3.42.3; id set to the record ID; body with exp_aprovado, exp_justificativa and exp_dtaprovado filled in.

Example 2: Bulk-update records from a spreadsheet

id = {{$json.id}}; body built with expressions from each input item's columns, so one PUT runs per row.

Links

Discussion