IntelupInstall

Summary

Updates an existing event movement in the Intelup API by ID, sending a JSON body with the movement's fields via a PUT request.

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 (required) — ID of the event movement to update. URL-encoded and substituted into the request path.
• body__putPublicEventMovementById (required) — JSON request body. Must be valid JSON or the node errors with 'Body must be valid JSON'. The default example has fields such as 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.

Output shape

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

The request is sent once per input item, using the credential's base URL plus the token, code and unit-code headers. The exact HTTP path and method come from a generated version catalog that is not included in the source, so they are not shown here. If 'Continue On Fail' is enabled, a failed item returns {error: message} instead of stopping the workflow.

Examples

Example 1: Approve a movement and add a note

Version 3.42.3; Id set to the movement ID (for example from a previous node); Body JSON with mvf_approved and mvf_obs set to the new values.

Example 2: Cancel an event movement

Id = movement ID; Body JSON includes "mvf_canceled": "S" or the value the API expects, along with the other required movement fields.

Links

• n8n community nodes installation guide