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 updates an existing Project Charge in the Autotask system. It is useful for scenarios where you need to modify details of a specific charge associated with a project, such as adjusting billing amounts, descriptions, or other charge-related fields. For example, if a billing amount was entered incorrectly or additional details need to be added to a charge, this node allows you to update that information programmatically within an automation workflow.
Properties
| Name | Meaning |
|---|---|
| Charge ID | The unique identifier of the Project Charge to update. This is required to specify which charge record will be modified. |
| Fields | The set of fields and their new values to update on the Project Charge. This uses a resource mapper to define which fields to change and their corresponding values. |
Output
JSON
id- The unique identifier of the updated Project Charge.fields- The updated fields and their values after the update operation.status- The status of the update operation, indicating success or failure.
Dependencies
- Requires an API key credential for Autotask REST API authentication to perform update operations.
Troubleshooting
- Error: 'Charge ID' is missing or invalid - Ensure that the Charge ID provided corresponds to an existing Project Charge in Autotask.
- Error: Invalid field values in 'Fields' - Verify that the fields and values conform to Autotask's Project Charge schema and data types.
- Authentication errors - Confirm that the API key credential is valid and has sufficient permissions to update Project Charges.
- Network or API errors - Check network connectivity and Autotask API status if requests fail unexpectedly.