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 Items from the Autotask system using an advanced filtering mechanism. It allows users to specify complex query criteria in JSON format to filter Configuration Items according to their needs. This is useful for scenarios where you need to extract specific Configuration Items based on detailed conditions, such as retrieving all items matching certain attributes or statuses. For example, an IT service manager could use this to get all Configuration Items of a particular category or with specific custom field values.
Properties
| Name | Meaning |
|---|---|
| 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 must be between 1 and 500. |
| Advanced Filter | A required JSON string containing a 'filter' array that defines the Autotask API query criteria to filter Configuration Items. This allows for complex and precise queries. |
| 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 Configuration Item object instead of being nested inside a userDefinedFields array. |
Output
JSON
id- Unique identifier of the Configuration Item.name- Name of the Configuration Item.categoryId- Identifier of the Configuration Item's category.category_label- Human-readable label for the Configuration Item's category (if Add Reference Labels is enabled).picklistField_label- Human-readable label for any picklist field included in the response (if Add Picklist Labels is enabled).userDefinedFields- User-defined fields nested inside the userDefinedFields array, unless Flatten User-Defined Fields is enabled. - User-defined fields promoted to top-level properties 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 the Advanced Filter property will cause the node to fail. Ensure the JSON string is correctly formatted and contains a 'filter' array as per Autotask API documentation.
- Requesting too many records without enabling 'Get All' or setting a very high 'Max Records' may lead to performance issues or API limits.
- If no results are returned, verify that the filter criteria in the Advanced Filter are correct and match existing Configuration Items.
- Enabling Add Picklist Labels or Add Reference Labels when the fields do not have corresponding labels will result in no additional label fields being added.
- If user-defined fields are not appearing as expected, check the Flatten User-Defined Fields setting to control their nesting.
Links
- Autotask API Basic Query Calls - Official Autotask API documentation describing how to construct query filters for advanced data retrieval.