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 Project Note in the Autotask system. It is useful for modifying details of notes attached to projects, such as correcting information or adding new data. For example, a user can update the content or metadata of a project note by specifying its Note ID and the fields to change.
Properties
| Name | Meaning |
|---|---|
| Note ID | The unique identifier of the project note to update, required to specify which note to modify. |
| Fields | The set of fields and their new values to update on the project note. This uses a resource mapper to define which fields to change and their values. |
Output
JSON
id- The unique identifier of the updated project note.fields- The updated fields and their values of the project note after the update operation.
Dependencies
- Requires an API key credential for Autotask REST API authentication.
Troubleshooting
- Ensure the Note ID provided exists and is correct; otherwise, the update will fail with a not found error.
- Verify that the fields to update are valid and allowed to be changed; invalid fields may cause errors.
- Check API authentication credentials are correctly configured to avoid authorization errors.
- If the update fails, review the error message for details on missing required fields or invalid data formats.