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 Note in the Autotask system. It is useful for modifying the content or details of a note associated with a configuration item, such as adding additional information or correcting existing data. For example, a user can update the note text or other mapped fields of a specific Configuration Item Note by providing its Note ID and the fields to update.
Properties
| Name | Meaning |
|---|---|
| Note ID | The unique identifier of the Configuration Item Note to update. |
| Fields | The set of fields and their values to update on the Configuration Item Note. This uses a resource mapper to define which fields to modify and their new values. |
Output
JSON
id- The ID of the updated Configuration Item Note.fields- The updated fields and their values of the Configuration Item Note.status- The status or result of the update operation, indicating success or failure.
Dependencies
- Requires an API key credential for Autotask REST API authentication.
- Relies on the Autotask REST API endpoint for Configuration Item Notes.
Troubleshooting
- If the Note ID is invalid or does not exist, the node will throw an error indicating the note could not be found.
- Providing invalid or unsupported fields in the Fields property may cause the update to fail with a validation error.
- Network or authentication issues with the Autotask API will result in connection errors; ensure API credentials are correct and network access is available.
- Ensure that the resource is set to 'configurationItemNote' and operation to 'update' to avoid unsupported resource errors.