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 in the Autotask system by specifying its unique ID and mapping the desired fields to update. It is useful for automating the modification of configuration items, such as updating asset details, status, or custom fields, without manual intervention. For example, it can be used to update the status of a configuration item after a maintenance task or to change ownership information programmatically.
Properties
| Name | Meaning |
|---|---|
| Configuration Item ID | The unique identifier of the configuration item to update. This is required to specify which item will be modified. |
| Fields | A resource mapper input that defines which fields of the configuration item should be updated and their new values. It supports defining fields manually or using auto-mapping features. |
Output
JSON
id- The unique identifier of the updated configuration item.fields- An object containing the updated fields and their new values as saved in Autotask.status- The status of the update operation, e.g., success or failure indication.message- Additional information or error messages related to the update operation.
Dependencies
- Requires an Autotask API key credential for authentication to access and modify configuration items via the Autotask REST API.
Troubleshooting
- If the Configuration 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 required fields are missing or the field mapping is incorrect, the update may fail with validation errors. Ensure all mandatory fields are included and correctly mapped.
- Authentication errors may occur if the API key credential is invalid or expired. Confirm the credential is valid and has sufficient permissions.
- Network or API rate limit issues can cause failures. Check network connectivity and Autotask API usage limits.