Intelup icon

Intelup

Interact with the Intelup API

Actions335

tag → Post Tag Operating Range Tag By Id

AI-generated

Summary

Sends a POST request to the Intelup API to apply a tag operating range, identified by Operating Range Id, using a JSON body. The exact HTTP path is defined in generated catalog files that are not included in the source pack.

Inputs

  • version (required) — Intelup API version snapshot to use: 3.42.3 (default), 3.41.6, or 3.41.5. Selects which operation definition is called.
  • operating_range_id (required) — Id of the operating range. It is URL-encoded and substituted into the request path.
  • body__postPublicTagOperatingRangeTagById (required) — JSON request body (Body (JSON)). It is parsed before sending, and the node errors with 'Body must be valid JSON' if parsing fails. Defaults to {}. The node falls back to a legacy 'body' parameter if this one is empty or {}.

Output shape

One output item per input item, with the Intelup API's JSON response as the item's json.

Requests are authenticated with the fenixApi credential (baseUrl, token, code, unit-code headers). If 'Continue On Fail' is enabled, a failed item returns {error: message}. Otherwise the node throws. The response schema isn't visible in the source.

Examples

Example 1: Apply a tag operating range for each incoming record

Version 3.42.3, Operating Range Id set to an expression such as {{$json.rangeId}}, Body (JSON) set to the payload the Intelup API expects for the tag.

Links

Discussion