IntelupInstall

Summary

Creates a new event motive (reason) in Intelup by sending a user-supplied JSON body to the public event-motive endpoint of the Intelup (Fenix) API.

Inputs

• version — Intelup API version to target: 3.42.3 (default), 3.41.6 or 3.41.5. Selects which operation catalog entry is used.
• body__postPublicEventMotive (required) — JSON request body describing the motive. The default example is {"mot_planejado":"S","mot_aprovacao":"S","color":"#000000"} (planned flag, approval flag, hex color). Must be valid JSON or the node throws 'Body must be valid JSON'. Field meanings are inferred from names only; the full schema is not in the node source.

Output shape

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

The HTTP method and path come from a bundled version catalog not shown in the source, so they are not stated here. Requests authenticate with the fenixApi credential (token, code, unit-code headers) against the configured base URL. The body is parsed once per input item. With Continue On Fail enabled, failed items return {error: message} instead of stopping the workflow.

Examples

Example 1: Register a new planned, approval-required event motive with a custom color

Version 3.42.3; Body: {"mot_planejado":"S","mot_aprovacao":"S","color":"#FF8800"}

Example 2: Create a non-planned motive that needs no approval

Version 3.42.3; Body: {"mot_planejado":"N","mot_aprovacao":"N","color":"#00AA00"}

Links

• n8n community nodes installation guide