IT Glue

Interact with the IT Glue API

Overview

This node interacts with the IT Glue API to perform operations on various resources, including Flexible Assets. Specifically, the 'Update' operation for the 'Flexible Asset' resource allows users to update a flexible asset record by specifying its ID, selecting a flexible asset type, and providing the relevant traits (fields) for that type. It supports additional query parameters and pagination options. This node is useful for automating updates to IT Glue flexible asset records within workflows, such as updating asset details based on external triggers or data changes.

Use Case Examples

  1. Updating a flexible asset's traits by specifying its ID and new field values.
  2. Automating bulk updates to flexible assets by iterating over input data and applying changes via the node.

Properties

Name Meaning
ID The unique identifier of the flexible asset record to update.
Flexible Asset Type The type of flexible asset to update, selected from available flexible asset types.
Traits The fields and their values for the selected flexible asset type to update.
Query Additional query parameters to customize the update request.
Return All Whether to return all results or limit the output.
Page Size The number of records to return per page, with a minimum of 1 and maximum of 1000.

Output

JSON

  • json
    • id - The ID of the updated flexible asset record.
    • flexibleAssetTypeId - The type ID of the flexible asset.
    • traits - The updated traits (fields) of the flexible asset.
    • updatedAt - Timestamp of when the flexible asset was last updated.

Dependencies

  • IT Glue API

Troubleshooting

  • Ensure the API credentials are correctly configured and have permissions to update flexible assets.
  • Verify that the flexible asset ID provided exists and is correct to avoid 'record not found' errors.
  • Check that the flexible asset type and traits match the expected schema to prevent validation errors from the API.
  • If the node fails, review error messages for details and consider enabling 'Continue On Fail' to handle errors gracefully in workflows.

Links

Discussion