Actions389
- Ticket History Actions
- Ticket Note Actions
- Ticket Note Webhook Actions
- Ticket Webhook Actions
- Time Entry Actions
- Resource Actions
- Resource Role Actions
- Role Actions
- Search Filter Actions
- Service Actions
- Service Call Actions
- Skill Actions
- Survey Actions
- Survey Results Actions
- Ticket Actions
- Invoice Actions
- Notification History Actions
- Opportunity Actions
- Product Actions
- Product Vendor Actions
- Project Actions
- Project Charge Actions
- Project Note Actions
- Project Phase Actions
- Project Task 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
- Contract Service Unit Actions
- Domain Registrar Actions
- Holiday Actions
- Holiday Set 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
- 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
- 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
- Billing Code Actions
- Company Actions
- Company Alert Actions
- Company Location Actions
- Company Note Actions
- Company Webhook Actions
- Configuration Item Actions
- Configuration Item Billing Product Association Actions
Contract Note → Update
AI-generatedOverview
This node interacts with the Autotask REST API to update an existing Contract Note identified by its Note ID. It allows users to modify specific fields of a Contract Note by mapping input data to the desired fields. This is useful in scenarios where contract notes need to be programmatically updated based on workflow data, such as updating status, content, or metadata of contract notes within an automated process.
Properties
| Name | Meaning |
|---|---|
| Note ID | The unique identifier of the Contract Note to update. This is required to specify which note will be modified. |
| Fields | A resource mapper input that defines which fields of the Contract Note should be updated and their new values. It supports defining fields manually or using auto-mapping features to map input data to Contract Note fields. |
Output
JSON
id- The unique identifier of the updated Contract Note.fields- The updated fields and their new values of the Contract Note.updatedAt- Timestamp indicating when the Contract Note was last updated.
Dependencies
- Requires an Autotask API key credential for authentication to access the Autotask REST API.
Troubleshooting
- If the Note ID is missing or invalid, the node will fail to locate the Contract Note to update. Ensure the Note ID is correct and exists.
- Incorrect field mappings or unsupported fields may cause the update operation to fail. Verify that the fields specified in the Fields property are valid for Contract Notes.
- API authentication errors may occur if the Autotask API key credential is missing, expired, or invalid. Check the credential configuration.
- Network or API rate limit issues can cause operation failures. Retry after some time or check API usage limits.