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 Company Note in the Autotask system. It is useful for users who need to modify details of notes attached to companies, such as updating descriptions, statuses, or other note-related fields. For example, a user can update the content of a note to reflect recent communications or changes in company status.
Properties
| Name | Meaning |
|---|---|
| Note ID | The unique identifier of the company note to update. This is required to specify which note will be modified. |
| Fields | The set of fields and their values to update on the company note. This uses a resource mapper to define which fields to change and their new values. |
Output
JSON
id- The unique identifier of the updated company note.fields- The updated fields of the company note reflecting the changes made.status- The status or result of the update operation, indicating success or failure.
Dependencies
- Requires an Autotask API key credential for authentication to access and modify company notes via the Autotask REST API.
Troubleshooting
- If the Note ID is invalid or does not exist, the node will throw an error indicating the note could not be found. Verify the Note ID is correct.
- If required fields in the update are missing or invalid, the API may reject the update. Ensure all mandatory fields are provided and valid.
- Authentication errors may occur if the API key credential is missing or invalid. Confirm the credential is configured properly.
- Network or API downtime can cause failures. Retry the operation after some time or check Autotask service status.