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 updates an existing Configuration Item Type in the Autotask system. It is useful for modifying the properties or fields of a configuration item type identified by its unique ID. For example, you can update the name, description, or custom fields of a configuration item type to keep your asset management data accurate and up to date.
Properties
| Name | Meaning |
|---|---|
| Configuration Item Type ID | The unique identifier of the configuration item type to update. This is required to specify which configuration item type will be modified. |
| Fields | The set of fields and their values to update on the configuration item type. This uses a resource mapper to define which fields to modify and their new values. |
Output
JSON
id- The unique identifier of the updated configuration item type.name- The name of the configuration item type after update.description- The description of the configuration item type after update.customFields- Any custom fields associated with the configuration item type, reflecting updated values.
Dependencies
- Requires an API key credential for Autotask REST API authentication.
Troubleshooting
- Ensure the Configuration Item Type ID is correct and exists in the Autotask system; otherwise, the update will fail with a not found error.
- Verify that the fields provided in the 'Fields' property are valid and allowed to be updated; invalid fields may cause errors.
- Check that the API credentials are valid and have sufficient permissions to perform update operations on configuration item types.
- Common error messages include 'Resource not found' if the ID is invalid, or 'Invalid field' if unsupported fields are included. Resolving these involves correcting the ID or field mappings respectively.