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 Billing Rule in the Autotask system. It allows users to modify specific fields of a contract billing rule identified by its unique ID. This is useful for automating updates to billing rules within contracts, such as changing billing parameters or conditions without manual intervention. For example, a user can update the billing rate or conditions of a contract billing rule as part of a workflow that manages contract lifecycle or billing adjustments.
Properties
| Name | Meaning |
|---|---|
| Billing Rule ID | The unique identifier of the contract billing rule to update. This is required to specify which billing rule will be modified. |
| Fields | A resource mapper input that defines which fields of the contract billing rule should be updated and their new values. It supports defining the mapping below and can auto-map fields if supported. |
Output
JSON
id- The unique identifier of the updated contract billing rule.fields- The updated fields and their 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 Autotask REST API authentication to perform update operations.
Troubleshooting
- If the Billing Rule ID is missing or invalid, the node will throw an error indicating the billing rule cannot be found.
- Incorrect or unsupported field mappings in the 'Fields' property may cause the update to fail or be ignored.
- API authentication errors may occur if the provided credentials are invalid or expired; ensure the API key credential is correctly configured.
- Network or API rate limit issues can cause operation failures; retry or check API usage limits.