Actions524
- AI Helper Actions
- Tool Actions
- API Threshold Actions
- Appointment Actions
- Billing Code Actions
- Billing Items Actions
- Change Request Link Actions
- Checklist Library Actions
- Checklist Library Item Actions
- Classification Icon Actions
- Company Actions
- Company Alert Actions
- Company Location Actions
- Company Note Actions
- Company Webhook Actions
- Company Site Configuration Actions
- Configuration Item Actions
- Configuration Item Billing Product Association 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
- Contact Actions
- Contact Webhook Actions
- Contact Groups Actions
- Contact Group Contacts Actions
- Contract Actions
- Contract Block Actions
- Contract Block Hour Factor Actions
- Contract Billing Rule Actions
- Contract Charge Actions
- Contract Exclusion Billing Code 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 Rate Actions
- Contract Role Costs Actions
- Contract Retainer Actions
- Contract Service Actions
- Contract Service Adjustment Actions
- Contract Service Bundle Adjustment Actions
- Contract Service Bundle Actions
- Contract Service Bundle Unit Actions
- Contract Ticket Purchase Actions
- Department Actions
- Project Phase Actions
- Quote Item Actions
- Quote Location Actions
- Quote Template Actions
- Resource Actions
- Resource Role Actions
- Resource Role Queue Actions
- Search Filter Actions
- Service Actions
- Service Call Actions
- Subscription Actions
- Subscription Period Actions
- Ticket Category Actions
- Ticket Category Field Default Actions
- Ticket History Actions
- Ticket Note Actions
Company Note → Update
AI-generatedOverview
This node operation updates an existing Company Note in Kaseya's Autotask PSA system. It is useful for scenarios where you need to modify details of a company note, such as updating the content or metadata associated with the note. For example, a user might update a note to reflect new information about a company or correct previous entries.
Use Case Examples
- Updating a company note to add additional comments or correct information.
- Modifying the note's fields to reflect changes in company status or interactions.
Properties
| Name | Meaning |
|---|---|
| Dry Run | Whether to return a request preview instead of executing the operation. Useful for testing and validation. |
| Impersonation Resource ID | Optional resource ID to impersonate for write requests. Leave blank to write as the credential user. |
| Proceed Without Impersonation If Denied | Whether to retry denied impersonated writes once without impersonation and proceed as the API user. Only applies when Impersonation Resource ID is set. |
| Fields | Fields to map and update on the company note. This defines which note properties will be changed. |
| Note ID | The ID of the company note to update. |
Output
JSON
id- The unique identifier of the updated company note.fields- The updated fields of the company note as per the input mapping.
Dependencies
- An API key credential for Kaseya's Autotask PSA REST API is required to authenticate and perform the update operation.
Troubleshooting
- If the note ID is invalid or not found, the node will throw an error indicating the note cannot be updated.
- If impersonation is used and denied, the operation can optionally retry without impersonation if configured.
- Errors related to API authentication or permissions will prevent the update operation from succeeding. Verify credentials and permissions.
Links
- Autotask REST API Documentation - Official documentation for Kaseya's Autotask REST API, useful for understanding the API endpoints and data structures.