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 Configuration Item Billing Product Association in Autotask. It is useful for automating the modification of billing product associations linked to configuration items, such as updating pricing or product details. For example, it can be used to programmatically adjust billing product associations when configuration items change or when billing details need to be synchronized with other systems.
Properties
| Name | Meaning |
|---|---|
| Billing Product Association ID | The unique identifier of the billing product association to update. This is required to specify which association record will be modified. |
| Fields | The set of fields and their values to update on the billing product association. This uses a resource mapper to define which fields to modify and their new values. |
Output
JSON
id- The ID of the updated billing product association.fields- The updated fields and their values after the update operation.success- Boolean indicating whether the update operation was successful.message- Optional message returned from the API, such as error details or confirmation.
Dependencies
- Requires an Autotask API key credential for authentication to the Autotask REST API.
Troubleshooting
- If the Billing Product Association ID is missing or invalid, the node will fail to locate the record to update. Ensure the ID is correct and exists in Autotask.
- Incorrect or incomplete field mappings in the 'Fields' property can cause the update to fail or produce unexpected results. Verify that the fields and values conform to Autotask's API requirements.
- Authentication errors may occur if the API key credential is invalid or expired. Confirm that the credential is properly configured and has necessary permissions.
- Network or API rate limit issues can cause timeouts or errors. Retry after some time or check API usage limits.