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 operation retrieves multiple Configuration Item Types from the Autotask system using an advanced filter query. It is useful for users who need to fetch Configuration Item Types based on complex criteria, such as specific attributes or conditions defined in the Autotask API query language. For example, a user can filter Configuration Item Types by category, status, or custom fields to get a tailored list for reporting or automation purposes.
Properties
| Name | Meaning |
|---|---|
| Get All | Determines whether to return all matching Configuration Item Types or limit the results to a specified maximum number. |
| Max Records | Specifies the maximum number of Configuration Item Types to return when 'Get All' is false. The value must be between 1 and 500. |
| Advanced Filter | A required JSON string containing a 'filter' array that defines the query criteria according to the Autotask API. This allows complex filtering of Configuration Item Types based on various fields. |
| Add Picklist Labels | If enabled, adds additional fields with '_label' suffix for picklist fields to provide human-readable values instead of raw codes. |
| Add Reference Labels | If enabled, adds additional fields with '_label' suffix for reference fields to provide human-readable values. |
| Select Columns Names or IDs. | Allows selection of specific fields to include in the response. If no fields are selected, all fields are returned. The ID field is always included. |
| Flatten User-Defined Fields | If enabled, user-defined fields (UDFs) are moved to the top level of each returned object instead of being nested inside a userDefinedFields array. |
Output
JSON
id- Unique identifier of the Configuration Item Type.name- Name of the Configuration Item Type.description- Description of the Configuration Item Type.categoryId- Identifier of the category this Configuration Item Type belongs to.picklistField_label- Human-readable label for picklist fields if 'Add Picklist Labels' is enabled.referenceField_label- Human-readable label for reference fields if 'Add Reference Labels' is enabled.userDefinedFields- User-defined fields nested inside userDefinedFields array or flattened to top-level if 'Flatten User-Defined Fields' is enabled.
Dependencies
- Requires an Autotask API key credential for authentication to access the Autotask REST API.
Troubleshooting
- Invalid JSON in 'Advanced Filter' property can cause query failures. Ensure the JSON string is correctly formatted and contains a valid 'filter' array as per Autotask API documentation.
- Requesting too many records without 'Get All' enabled may result in incomplete data. Use 'Get All' to retrieve all matching records if needed.
- Selecting fields that do not exist or are misspelled in 'Select Columns' may cause errors or missing data in the response.
- If picklist or reference labels are not appearing, verify that 'Add Picklist Labels' and 'Add Reference Labels' are enabled and that the fields contain values.
- API rate limits or authentication errors may occur if the Autotask API key is invalid or has insufficient permissions.
Links
- Autotask API Basic Query Calls - Official Autotask documentation on how to construct advanced filter queries for API calls.