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 Category in the Autotask system. It is useful for modifying details of a configuration item category by specifying its unique ID and the fields to update. For example, you can change the name or description of a category to keep your configuration management database accurate and up to date.
Properties
| Name | Meaning |
|---|---|
| Configuration Item Category ID | The unique identifier of the configuration item category to update. |
| Fields | The specific fields and their new values to update on the configuration item category, defined using a resource mapper to specify which fields to change. |
Output
JSON
id- The ID of the updated configuration item category.name- The name of the updated configuration item category.description- The description of the updated configuration item category.otherUpdatedFields- Any other fields that were updated and returned by the API.
Dependencies
- Requires an API key credential for Autotask REST API authentication.
Troubleshooting
- Ensure the Configuration Item Category ID is correct and exists in Autotask; otherwise, the update will fail.
- Verify that the fields to update are valid and allowed to be changed; invalid fields may cause errors.
- Check API credentials and network connectivity if the node cannot connect to Autotask API.
- If the API returns permission errors, confirm that the API key has sufficient rights to update configuration item categories.