Intelup icon

Intelup

Interact with the Intelup API

Actions335

legacy → Post Legacy Int Expdadostpf

AI-generated

Summary

Sends a JSON body to the Intelup API's legacy "int/expdadostpf" endpoint (postPublicLegacyIntExpdadostpf) to submit tag/period data records, authenticating with the node's Intelup credentials.

Inputs

  • version (required) — Intelup API version to target: 3.42.3 (default), 3.41.6, or 3.41.5. Determines which operation definition is used.
  • body__postPublicLegacyIntExpdadostpf (required) — JSON request body. The template includes 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, exp_dtaprovado. The placeholder values ('The task details') must be replaced with real data. Must be valid JSON or the node errors with 'Body must be valid JSON'.

Output shape

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

The request is made once per input item, as a POST with token, code and unit-code headers taken from the credentials. The body is parsed from the parameter, and an expression can reference each item. With Continue On Fail enabled, a failed item yields {error: message} instead of stopping the workflow. The response schema is not defined in the source.

Examples

Example 1: Push an approved expense data record for a tag from upstream data

Version 3.42.3; Body JSON with plt_codigo, cli_codigo, tag_codigo, exp_data, exp_valor_str set via expressions from the incoming item; exp_aprovado set to the desired value.

Links

Discussion