Autotask icon

Autotask

Consume Autotask REST API
Join our community

Actions389

Overview

This node operation retrieves multiple Configuration Items from the Autotask system. It is useful for scenarios where you need to fetch a list of configuration items, such as for inventory management, asset tracking, or reporting purposes. For example, you can use it to get all configuration items related to a specific project or to analyze the current assets in your IT environment.

Properties

Name Meaning
Fields Defines which fields of the Configuration Items to retrieve and map in the output. Allows precise control over the data returned, including support for user-defined fields and automatic mapping.
Get All Determines whether to return all matching Configuration Items or limit the number of results.
Max Records Specifies the maximum number of Configuration Items to return when 'Get All' is false. The value can range from 1 to 500.
Add Picklist Labels If enabled, adds human-readable label fields for picklist fields in the output, enhancing readability.
Add Reference Labels If enabled, adds human-readable label fields for reference fields in the output.
Select Columns Names or IDs. Allows selection of specific fields to include in the response by choosing from a list or specifying IDs via expressions. If no fields are selected, all fields are returned. The ID field is always included.
Flatten User-Defined Fields When enabled, user-defined fields (UDFs) are promoted to top-level properties in each Configuration Item object instead of being nested inside a userDefinedFields array.

Output

JSON

  • configurationItems - An array of Configuration Item objects retrieved from Autotask, each containing the requested fields and optionally additional label fields and flattened user-defined fields.

Dependencies

  • Requires an Autotask API key credential for authentication to access the Autotask REST API.

Troubleshooting

  • If the node returns no data, verify that the 'Fields' property is correctly configured to include the desired fields and that the Autotask account has access to Configuration Items.
  • If the node fails with authentication errors, ensure that the Autotask API credentials are correctly set up and have sufficient permissions.
  • When selecting specific columns, if some fields are missing or cause errors, check that the field IDs or names are valid and supported by the Autotask API for Configuration Items.
  • If the output is missing expected human-readable labels, verify that 'Add Picklist Labels' and 'Add Reference Labels' options are enabled.
  • If user-defined fields are not appearing as expected, check the 'Flatten User-Defined Fields' option to control their structure in the output.

Discussion