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 operation updates an existing contract in the Autotask system by specifying the contract's unique ID and mapping the desired fields to update. It is useful for automating contract modifications such as changing terms, dates, or other contract details without manual intervention. For example, it can be used to update contract expiration dates or adjust contract parameters based on external triggers.
Properties
| Name | Meaning |
|---|---|
| Contract ID | The unique identifier of the contract to update, required to specify which contract record to modify. |
| Fields | A resource mapper input that defines which contract fields to update and their new values. Supports defining fields manually or auto-mapping from input data. |
Output
JSON
id- The unique identifier of the updated contract.fields- The updated fields and their new values after the update operation.status- The status or result of the update operation, indicating success or failure.
Dependencies
- Requires an API key credential for authenticating with the Autotask REST API.
Troubleshooting
- Ensure the Contract ID provided exists and is valid; otherwise, the update will fail with a not found error.
- Verify that the fields mapped for update are valid contract fields supported by the Autotask API to avoid validation errors.
- Check API authentication credentials if the node fails to connect or returns authorization errors.
- If the update operation returns an error, review the error message for details on invalid data or missing required fields and adjust the input accordingly.