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 Category User-Defined Field (UDF) Association from the Autotask system by its unique ID. It is useful for users who need to fetch detailed information about how user-defined fields are associated with configuration item categories, enabling integration or automation workflows that depend on these associations. For example, it can be used to synchronize configuration item category UDF associations with other systems or to display detailed configuration metadata in a dashboard.
Properties
| Name | Meaning |
|---|---|
| Configuration Item Category UDF Association ID | The unique identifier of the configuration item category UDF association to retrieve. |
| Add Picklist Labels | Determines whether to automatically add human-readable "_label" fields for picklist fields in the response, enhancing readability by including label values alongside raw data. |
| Add Reference Labels | Determines whether to automatically add human-readable "_label" fields for reference fields in the response, providing more understandable output for reference data. |
| Select Columns Names or IDs. | Specifies which fields to include in the response. If no fields are selected, all fields are returned. The ID field is always included regardless of selection. |
| Flatten User-Defined Fields | If enabled, user-defined fields (UDFs) are brought to the top level of each returned object instead of being nested inside a userDefinedFields array, simplifying access to these fields. |
Output
JSON
id- The unique identifier of the configuration item category UDF association.fieldName_label- Human-readable labels for picklist or reference fields if addPicklistLabels or addReferenceLabels is enabled.
userDefinedFields- Array of user-defined fields associated with the configuration item category, unless flattenUdfs is enabled.
Dependencies
- Requires an authenticated connection to the Autotask REST API via an API key credential.
Troubleshooting
- Ensure the Configuration Item Category UDF Association ID provided is valid and exists in the Autotask system; invalid IDs will cause errors.
- If no data is returned, verify that the selected columns include fields that exist and that the user has permission to access them.
- If labels are not appearing as expected, check that addPicklistLabels and addReferenceLabels are enabled and that the fields have non-empty values.
- Flattening UDFs may cause naming conflicts if UDF names overlap with standard fields; disable flattenUdfs if this occurs.