Actions389
- Contract Actions
- Ticket History Actions
- Ticket Note Webhook Actions
- Ticket Note Actions
- Ticket Webhook Actions
- Time Entry Actions
- Resource Actions
- Role Actions
- Resource Role Actions
- Search Filter Actions
- Service Actions
- Skill Actions
- Service Call Actions
- Survey Results Actions
- Survey Actions
- Ticket Actions
- Opportunity Actions
- Notification History Actions
- Invoice Actions
- Product Actions
- Product Vendor Actions
- Project Actions
- Project Charge Actions
- Project Phase Actions
- Project Task Actions
- Project Note Actions
- Contract Retainer Actions
- Contract Service Actions
- Contract Service Adjustment Actions
- Contract Service Bundle Actions
- Contract Service Bundle Unit Actions
- Contract Service Bundle Adjustment Actions
- Contract Ticket Purchase Actions
- Contract Service Unit Actions
- Domain Registrar Actions
- Holiday Actions
- Holiday Set Actions
- Contract Exclusion Billing Code Actions
- Contract Rate Actions
- Contract Exclusion Role Actions
- Contract Exclusion Sets Actions
- Contract Exclusion Set Excluded Role Actions
- Contract Exclusion Set Excluded Work Type Actions
- Contract Milestone Actions
- Contract Note Actions
- Contract Role Costs Actions
- Contact Groups Actions
- Contact Actions
- Contact Webhook Actions
- Contact Group Contacts Actions
- Contract Block Hour Factor Actions
- Contract Block Actions
- Contract Billing Rule Actions
- Contract Charge Actions
- Configuration Item Category Actions
- Configuration Item Category UDF Association Actions
- Configuration Item DNS Record Actions
- Configuration Item Note Actions
- Configuration Item Related Item Actions
- Configuration Item SSL Subject Alternative Name Actions
- Configuration Item Type Actions
- Configuration Item Webhook Actions
- Company Alert Actions
- Company Actions
- Billing Code Actions
- Company Location Actions
- Company Note Actions
- Company Webhook Actions
- Configuration Item Actions
- Configuration Item Billing Product Association Actions
Overview
This node interacts with the Autotask REST API to retrieve detailed information about a specific Configuration Item Type by its ID. It is useful for IT service management workflows where understanding or manipulating configuration item types is necessary, such as asset management, change management, or CMDB integrations. For example, a user can fetch a configuration item type's metadata to automate asset categorization or to synchronize configuration data with other systems.
Properties
| Name | Meaning |
|---|---|
| Configuration Item Type ID | The unique identifier of the configuration item type to retrieve. |
| Add Picklist Labels | Determines whether to add human-readable '_label' fields for picklist fields in the response, enhancing readability by including labels alongside raw values. |
| Add Reference Labels | Determines whether to add human-readable '_label' fields for reference fields in the response, providing clearer context for referenced entities. |
| Select Columns Names or IDs. | Specifies which fields to include in the response. If none 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) are promoted to top-level properties in the output object instead of being nested inside a userDefinedFields array. |
Output
JSON
id- The unique identifier of the configuration item type.name- The name of the configuration item type.description- A textual description of the configuration item type.fields- An object or array containing the selected fields of the configuration item type, including standard and user-defined fields.picklistLabels- Additional '_label' fields for picklist fields providing human-readable labels, if enabled.referenceLabels- Additional '_label' fields for reference fields providing human-readable labels, if enabled.userDefinedFields- Array of user-defined fields, unless flattened to top-level properties.
Dependencies
- Requires an Autotask API key credential for authentication to access the Autotask REST API.
Troubleshooting
- If the Configuration Item Type ID is invalid or not found, the node will throw an error indicating the resource could not be retrieved. Verify the ID is correct.
- If authentication fails, ensure the Autotask API credentials are correctly configured and have sufficient permissions.
- Selecting specific columns that do not exist may result in incomplete data or errors; verify field names or IDs are valid.
- Enabling 'Add Picklist Labels' or 'Add Reference Labels' when the fields have empty values will not add labels, which is expected behavior.
- Flattening user-defined fields may cause naming conflicts if UDF names overlap with standard fields; use with caution.