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
Contract → Update
AI-generatedOverview
This node operation updates an existing contract in the Autotask PSA system. It is useful for scenarios where you need to modify contract details such as terms, billing rules, services, or other contract-related information. For example, you might update a contract's billing rules or service details based on changes in client agreements or project scope.
Use Case Examples
- Updating the billing rules of a contract to reflect new pricing.
- Modifying contract service details to add or remove services.
- Changing contract terms or milestones as per client requests.
Properties
| Name | Meaning |
|---|---|
| Contract ID | The ID of the contract to operate on, used to identify which contract to update. |
| Dry Run | Whether to return a request preview instead of executing the operation. Useful for testing and validation without making actual changes. |
| Fields | The fields of the contract to update, mapped using a resource mapper to define which contract properties to change. |
Output
JSON
id- The unique identifier of the updated contract.fieldsUpdated- Details of the fields that were updated in the contract.status- The status of the update operation, indicating success or failure.
Dependencies
- Requires an API key credential for Autotask PSA REST API access.
Troubleshooting
- Ensure the Contract ID is valid and exists in the Autotask system to avoid errors.
- If Dry Run is enabled, no changes will be made; disable it to perform actual updates.
- Check API credentials and permissions if the update operation fails due to authentication issues.
- Handle errors gracefully by enabling 'Continue On Fail' to capture error messages per item.
Links
- Autotask PSA REST API Documentation - Official documentation for Autotask PSA REST API, useful for understanding contract update operations.