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 deletes a specific contract charge within the Autotask system. It requires the user to specify both the Contract ID and the Charge ID to identify the exact charge to be removed. This operation is useful for managing contract billing details by removing outdated or incorrect charges associated with a contract.
Properties
| Name | Meaning |
|---|---|
| Charge ID | The unique identifier of the charge to be deleted within the specified contract. |
| Contract ID | The unique identifier of the contract that the charge belongs to. |
Output
JSON
success- Indicates whether the deletion of the contract charge was successful (true/false).message- A message providing additional information about the deletion result, such as confirmation or error details.
Dependencies
- Requires an authenticated connection to the Autotask REST API using an API key credential.
Troubleshooting
- If the Charge ID or Contract ID is incorrect or does not exist, the node will fail to delete the charge. Verify that both IDs are accurate.
- Authentication errors may occur if the API key credential is missing or invalid. Ensure proper API credentials are configured.
- Network or API availability issues can cause operation failures. Check network connectivity and Autotask service status.
- Error messages typically indicate missing parameters, invalid IDs, or permission issues. Review the error details and confirm user permissions.