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 Related Items from the Autotask system. It is useful for scenarios where you need to fetch a list of related items associated with configuration items, such as for asset management, IT service management, or auditing purposes. For example, you can use it to get all related hardware or software components linked to a specific configuration item in your IT environment.
Properties
| Name | Meaning |
|---|---|
| Fields | Defines which fields to map and include in the output for each Configuration Item Related Item. This allows selecting specific data points to retrieve. |
| Get All | Determines whether to return all matching records or limit the number of records returned. |
| Max Records | Specifies the maximum number of Configuration Item Related 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, making it easier to understand picklist values. |
| Add Reference Labels | If enabled, adds human-readable label fields for reference fields in the output, improving readability of referenced data. |
| Select Columns Names or IDs. | Allows selecting specific columns (fields) to include in the response. If none are selected, all fields are returned. The ID field is always included. |
| Flatten User-Defined Fields | If enabled, user-defined fields (UDFs) are brought to the top level of each object instead of being nested, simplifying access to these fields. |
Output
JSON
id- Unique identifier of the Configuration Item Related Item.fields*- Selected fields of the Configuration Item Related Item as specified by the 'Fields' property.*_label- Human-readable labels for picklist or reference fields if 'Add Picklist Labels' or 'Add Reference Labels' are enabled.
userDefinedFields- Array of user-defined fields unless 'Flatten User-Defined Fields' is enabled.
Dependencies
- Requires an Autotask API key credential for authentication to access the Autotask REST API.
Troubleshooting
- If no records are returned, verify that the Configuration Item Related Items exist and that the correct filters or fields are selected.
- If the node fails with authentication errors, ensure the Autotask API credentials are correctly configured and valid.
- Selecting too many fields or returning all records may lead to performance issues or timeouts; consider limiting the number of records or fields.
- If picklist or reference labels are missing, check that the corresponding options 'Add Picklist Labels' and 'Add Reference Labels' are enabled.