Intelup icon

Intelup

Interact with the Intelup API

Actions335

event → Put Event Destination Step By Id Event Movement By Id

AI-generated

Summary

Updates an existing movement record (by id_movfr) belonging to an event destination step (by id_dest_step) in the Intelup (Fenix) API, using a PUT request with a JSON body.

Inputs

  • version (required) — Intelup API version to target (3.42.3, 3.41.6, or 3.41.5); default 3.42.3. Determines which operation definition is used.
  • id_dest_step (required) — ID of the event destination step; substituted into the request URL path.
  • id_movfr (required) — ID of the event movement to update; substituted into the request URL path.
  • body__putPublicEventDestinationStepByIdEventMovementById (required) — JSON body with the movement fields to send. Example fields: mvf_input, types, mvf_ini, mvf_fim, mvf_dt_create, mvf_obs, mvf_os, mvf_break_day_start, mvf_break_day_end, mvf_approved, mvf_canceled. Must be valid JSON or the node errors.

Output shape

One output item per input item, containing the JSON response returned by the Intelup API.

Authenticates with the fenixApi credential (token, code, unit-code headers) against the configured base URL. The exact URL path template comes from a generated catalog not shown here. With Continue On Fail enabled, failed items return {error: message} instead of stopping the workflow.

Examples

Example 1: Approve a movement on an event destination step

Set id_dest_step and id_movfr to the target IDs, and body to {"mvf_approved":"Y","mvf_obs":"Reviewed"} (adjust to the fields the API accepts).

Example 2: Cancel a movement

Provide the two IDs and a body with "mvf_canceled": "Y" plus the other required movement fields.

Links

Discussion