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 Contract Service Bundle in the Autotask system. It allows users to specify the ID of the service bundle they want to update and map the fields they wish to modify. This is useful for automating contract management workflows, such as adjusting service bundle details programmatically based on external triggers or data changes.
Properties
| Name | Meaning |
|---|---|
| Service Bundle ID | The unique identifier of the contract service bundle to update. This is required to specify which service bundle record will be modified. |
| Fields | A resource mapper input that defines which fields of the contract service bundle should be updated and their new values. It supports defining fields manually or using auto-mapping features to streamline updates. |
Output
JSON
id- The ID of the updated contract service bundle.fields- The updated fields and their new 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.
- Relies on the Autotask REST API endpoint for contract service bundles.
Troubleshooting
- If the Service Bundle 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 field mappings or unsupported fields may cause the update to fail. Verify that the fields specified in the resource mapper are valid for contract service bundles.
- API authentication errors may occur if the API key credential is invalid or expired. Check and refresh credentials as needed.
- Network or API rate limit issues can cause operation failures. Implement retries or check Autotask API usage limits.