IntelupInstall

Summary

Submits a new event movement record to the Intelup (Fenix) API by sending a JSON body to the public event-movement endpoint. The HTTP method and path come from a generated version catalog not included in the source pack.

Inputs

• version (required) — Intelup API version to target (3.42.3, 3.41.6 or 3.41.5; default 3.42.3). Selects which operation definition is used.
• body__postPublicEventMovement (required) — JSON request body for the movement. The default example has mvf_input (e.g. "M"), types (array), mvf_ini, mvf_fim and mvf_dt_create (ISO timestamps), mvf_obs, mvf_os, mvf_break_day_start and mvf_break_day_end ("N"), mvf_approved (null) and mvf_canceled ("N"). Must be valid JSON or the node errors with 'Body must be valid JSON'.

Output shape

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

The node authenticates with the fenixApi credential (baseUrl, token, code, unit-code headers). It runs once per input item. With Continue On Fail enabled, a failed item returns {error: message} instead of stopping the workflow. The response schema is not defined in the source.

Examples

Example 1: Register a movement with start and end times and a note for an event

Version 3.42.3; Body JSON with mvf_input "M", mvf_ini and mvf_fim timestamps, mvf_obs text, mvf_canceled "N".

Example 2: Create movements from upstream data

Set Body (JSON) to an expression such as {{ JSON.stringify($json) }} so each incoming item posts its own movement.

Links

• n8n community nodes installation guide