IT Glue ExtendedInstall

Summary

Creates a new IT Glue flexible asset of a chosen type, optionally under a specific organization, with field values supplied as traits. Returns the created asset as a flattened record.

Inputs

• flexibleAssetTypeId (required) — Flexible asset type, chosen from a list loaded from IT Glue. Sent as the 'flexible-asset-type-id' attribute. The operation errors if empty.
• traits — JSON object of the form { "trait": [ { "name": "field-name-key", "value": ... } ] }. Entries without a name or with an undefined value are skipped. The remaining entries are sent as a name-to-value map. Defaults to an empty trait list. Field name-keys come from the asset type's fields.
• organizationId — Organization to create the asset under, chosen from a list or set by expression. If set, it is sent as 'organization-id' and the request is POSTed to organizations/{id}/relationships/flexible_assets. If empty, it is POSTed to flexible_assets.

Output shape

A single item containing the created flexible asset. Attributes are converted from kebab-case to camelCase (including the returned traits), plus id, type, and relationships if present.

Throws if IT Glue returns no data or if the type ID is missing. API errors (401, 403, 429 and others) are raised as node errors, and 429s are retried up to 3 times. With Continue On Fail enabled, the item contains an error message instead. The code reads traits as an object with a 'trait' array. A plain JSON string value may not be parsed by the code shown, so supply it as an object or via an expression.

Examples

Example 1: Add a new 'Server' asset to a specific client

Flexible Asset Type = Server; Organization = Acme Corp; Traits = {"trait":[{"name":"hostname","value":"srv01"},{"name":"ip-address","value":"10.0.0.5"}]}

Example 2: Create an asset from incoming workflow data

Flexible Asset Type chosen from list; Organization ID set by expression {{$json.orgId}}; Traits built with an expression from upstream fields

Links

• n8n community nodes installation guide