Autotask icon

Autotask

Consume Autotask REST API
Join our community

Actions389

Overview

This node operation retrieves a specific Configuration Item from the Autotask system by its unique ID. It is useful for scenarios where detailed information about a particular configuration item is needed, such as in IT service management workflows, asset tracking, or configuration audits. For example, a user can fetch a configuration item's details to display its current status, associated user-defined fields, or related references within an automation workflow.

Properties

Name Meaning
Configuration Item ID The unique identifier of the configuration item to retrieve.
Add Picklist Labels Determines whether to automatically add human-readable '_label' fields for picklist fields in the response. Labels are not added for empty values.
Add Reference Labels Determines whether to automatically add human-readable '_label' fields for reference fields in the response. Labels are not added for empty values.
Select Columns Names or IDs. Specifies which fields to include in the response. If no fields are selected, all fields are returned. The ID field is always included regardless of selection.
Flatten User-Defined Fields Determines whether user-defined fields (UDFs) should be brought up to the top level of the returned object instead of being nested inside the userDefinedFields array.

Output

JSON

  • id - The unique identifier of the configuration item.
  • name - The name of the configuration item.
    fields - Various standard and custom fields of the configuration item, including user-defined fields if flattening is disabled._label - Human-readable labels for picklist or reference fields, added if the respective options are enabled.
  • userDefinedFields - Array of user-defined fields associated with the configuration item, present if flattening is disabled.

Dependencies

  • Requires an API key credential for Autotask REST API authentication.

Troubleshooting

  • If the Configuration Item ID is invalid or not found, the node will throw an error indicating the item does not exist. Verify the ID is correct.
  • If API authentication fails, ensure the API key credential is correctly configured and has sufficient permissions.
  • Selecting specific columns that do not exist may result in incomplete data or errors; verify field names or IDs are valid.
  • Enabling flattening of user-defined fields may cause naming conflicts if UDF names overlap with standard fields.

Links

Discussion