IntelupInstall

Summary

Sends a POST request to the Intelup (Fenix) public API to add complementary item data to an event movement, identified by its Id, using a JSON body you supply.

Inputs

• Version (required) — Intelup API version snapshot to use (3.42.3 default, 3.41.6, or 3.41.5). Selects which operation definition is called.
• Id (required) — Identifier of the event movement. It is URL-encoded and substituted into the request path's {id} placeholder.
• Body (JSON) (required) — JSON payload sent as the request body (default {}). It must parse as valid JSON or the node throws 'Body must be valid JSON'. The expected fields are not declared in the node, so check the Intelup API docs.

Output shape

One output item per input item, with the parsed JSON response from the Intelup API in json.

The exact endpoint path comes from a generated catalog not included in the source, so it is not shown here. Auth uses the fenixApi credential (token, code and unit-code headers, plus base URL). With Continue On Fail enabled, failed items return {error: message} instead of stopping the workflow. The request runs once per input item.

Examples

Example 1: Attach complementary item details to a known event movement.

Version 3.42.3, Id set to the movement ID (e.g. from an earlier node via expression), Body JSON containing the complementary item fields required by the Intelup API.

Example 2: Bulk-process several movements from a spreadsheet.

Feed multiple items in; set Id to {{$json.movementId}} and Body to an expression-built JSON string; enable Continue On Fail to collect per-item errors.

Links

• n8n community nodes installation guide