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 Charge → Update
AI-generatedOverview
This node operation updates an existing Contract Charge in the Autotask PSA system. It is useful for scenarios where you need to modify details of a contract charge, such as adjusting billing amounts or updating charge descriptions. For example, a user might update a contract charge to reflect a change in service pricing or correct an error in the original charge data.
Use Case Examples
- Updating the billing amount of a contract charge to reflect a new agreed price.
- Modifying the description or other metadata of a contract charge to provide more accurate information.
Properties
| Name | Meaning |
|---|---|
| Dry Run | Whether to return a request preview instead of executing the operation. Useful for testing and validation. When enabled, no API call is made and no changes are made to Autotask. |
| Fields | Fields to map and update on the contract charge. This allows specifying which contract charge fields to modify and their new values. |
| Charge ID | The ID of the contract charge to update. This is required to identify which contract charge record to modify. |
Output
JSON
id- The ID of the updated contract charge.fieldsUpdated- Details of the fields that were updated in the contract charge.status- The status of the update operation, indicating success or failure.
Dependencies
- Requires an API key credential for Autotask PSA REST API authentication.
Troubleshooting
- Common issues include providing an invalid or missing Charge ID, which will cause the update to fail.
- If the Dry Run option is enabled, no actual update occurs; users should disable it to apply changes.
- Errors may occur if required fields for the update are missing or incorrectly formatted. Ensure all mandatory fields are correctly set.
Links
- Autotask PSA REST API Documentation - Official API documentation for Autotask PSA, useful for understanding the contract charge update operation and required fields.