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 a specific Configuration Item Related Item from the Autotask system by its unique Related Item ID. It is useful for scenarios where you need to fetch detailed information about a related item linked to a configuration item, such as for auditing, reporting, or integration purposes. For example, you might use this node to get details about a related hardware or software component associated with a configuration item in your IT asset management workflow.
Properties
| Name | Meaning |
|---|---|
| Related Item ID | The unique identifier of the related item to retrieve. |
| Add Picklist Labels | Determines whether to automatically add human-readable '_label' fields for picklist fields in the response, enhancing readability by showing labels instead of raw values. |
| Add Reference Labels | Determines whether to automatically add human-readable '_label' fields for reference fields in the response, making reference data easier to understand. |
| 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) should be moved to the top level of the returned object instead of being nested inside a userDefinedFields array. |
Output
JSON
id- The unique identifier of the related item.fields- Various fields of the related item as specified by the selected columns or all fields if none selected._label - Human-readable labels for picklist or reference fields if 'Add Picklist Labels' or 'Add Reference Labels' options are enabled.userDefinedFields- Array of user-defined fields associated with the related item, unless flattened to top-level properties.
Dependencies
- Requires an Autotask API key credential for authentication to access the Autotask REST API.
Troubleshooting
- If the Related Item ID is invalid or does not exist, the node will throw an error indicating the item was not found. Verify the ID is correct.
- If API authentication fails, ensure the Autotask API key credential is correctly configured and has sufficient permissions.
- Selecting invalid or non-existent columns in 'Select Columns' may result in incomplete or empty data fields.
- Enabling 'Add Picklist Labels' or 'Add Reference Labels' when the fields have empty values will not add label fields, which is expected behavior.
- If user-defined fields are not appearing as expected, check the 'Flatten User-Defined Fields' option to control their structure in the output.