Intelup icon

Intelup

Interact with the Intelup API

Actions335

event → Post Event Destination Step By Id Event Movement

AI-generated

Summary

Posts an event movement record to the Intelup (Fenix) API for a given destination step, identified by its ID. The HTTP method and path come from a generated catalog not included in the source pack, so the exact endpoint is not shown here.

Inputs

  • version (required) — API version to target: 3.42.3 (default), 3.41.6 or 3.41.5. It selects which operation definition is used.
  • id_dest_step (required) — ID of the destination step the movement belongs to. It is URL-encoded and substituted into the request path.
  • body__postPublicEventDestinationStepByIdEventMovement (required) — JSON request body describing the movement. The example includes 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"/"Y"), mvf_approved (null) and mvf_canceled ("N"). It must parse as valid JSON or the node throws "Body must be valid JSON".

Output shape

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

The request is sent once per input item, authenticated with the fenixApi credential's token, code and unit-code headers. 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 work-time movement on a destination step from an upstream trigger.

Version 3.42.3; id_dest_step set to an expression such as {{$json.stepId}}; body set to JSON with mvf_input "M", mvf_ini and mvf_fim timestamps, and mvf_obs notes.

Links

Discussion