IT Glue ExtendedInstall

Summary

Updates multiple IT Glue Configuration records in a single PATCH request to the configurations endpoint, using a JSON array of objects that each carry a record ID plus the attributes to change.

Inputs

• Items (bulkItems) (required) — JSON array (or a JSON string of one) of objects, each with an ID plus the attributes to change, e.g. [{"id":"123","name":"New"}]. It must be non-empty. The source reads the key as lowercase id and throws if it is missing or falsy for any item, even though the UI hint shows "ID". All other keys are sent unchanged as attributes. They are not converted from camelCase, so use IT Glue's kebab-case names such as serial-number or configuration-status-id.

Output shape

A list of output items, one per updated configuration returned by IT Glue. Attributes are flattened to the top level with kebab-case keys converted to camelCase, plus id, type, and relationships if present.

Errors if Items is invalid JSON, not an array, empty, or any element lacks id. API errors (401, 403, 429 and others) are raised as node errors, and 429s are retried up to 3 times. If the response has no data, the node emits {found: 0, resource, operation}. With Continue On Fail enabled, failures become {error} items. The request is sent as one batch, so IT Glue decides whether it applies partially or not at all.

Examples

Example 1: Mark several configurations as archived at once

Resource: Configuration, Operation: Bulk Update, Items: [{"id":"101","archived":true},{"id":"102","archived":true}]

Example 2: Change the status of devices built from upstream data

Items set by expression from earlier nodes, e.g. [{"id":"555","configuration-status-id":"12","notes":"Decommissioned"}]

Links

• n8n community nodes installation guide