IntelupInstall

Summary

Creates an event record in the Intelup (Fenix) API by sending a JSON body to the public event endpoint (operation key postPublicEventEvent) once for each input item.

Inputs

• version (required) — API version snapshot to use: 3.42.3 (default), 3.41.6, or 3.41.5. It selects which operation definition is used.
• body__postPublicEventEvent (required) — JSON request body describing the event. The Swagger-generated example has fields fra_descri, fra_codigo, fra_color, fra_status, fra_expdtm, fra_execreconcilia, fra_quebra_fim_dia, fra_ultimo_processamento, fra_ultima_execucao, fra_anular_parada, remaked_at, created_at, updated_at and deleted_at. The placeholder values must be replaced. The body must parse as valid JSON, or the node throws 'Body must be valid JSON'. It can use expressions to vary per item.

Output shape

One output item per input item. Each item's json is the API's response to the event creation request.

The node authenticates with the fenixApi credential (base URL, token, code and unit code sent as headers). The HTTP method and path come from the generated version catalog, which isn't shown in the source, so they aren't stated here. If Continue On Fail is enabled, a failed item returns {error: message}. Otherwise the node throws on the first error.

Examples

Example 1: Create an event with a code, description and status.

Version 3.42.3. Body JSON set to {"fra_codigo":"EVT01","fra_descri":"Delivery delay","fra_color":"#FF0000","fra_status":"A"}. The values here are illustrative, so check the Intelup API for the allowed ones.

Example 2: Create events in bulk from a spreadsheet.

Feed rows into the node. Set the body to an expression such as {{ JSON.stringify({fra_codigo: $json.code, fra_descri: $json.name}) }}. The node makes one request per row.

Links

• n8n community nodes installation guide