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 interacts with the Autotask REST API to update an existing Contract Service by its unique Service ID. It allows users to modify specific fields of a contract service within Autotask, enabling automation of contract management tasks such as updating service details or configurations. This is useful in scenarios where contract services need to be programmatically maintained or synchronized with other systems.
Properties
| Name | Meaning |
|---|---|
| Service ID | The unique identifier of the contract service to update. This is required to specify which service record will be modified. |
| Fields | A resource mapper input that defines which fields of the contract service should be updated and their new values. It supports defining fields manually or using auto-mapping features to streamline updates. |
Output
JSON
id- The unique identifier of the updated contract service.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 Autotask API key credential for authentication to access the Autotask REST API.
Troubleshooting
- If the Service ID is invalid or does not exist, the node will throw an error indicating the service could not be found. Verify the Service ID is correct.
- If required fields are missing or the fields to update are invalid, the API may reject the request. Ensure all mandatory fields are provided and field names are correct.
- Authentication errors may occur if the API key credential is missing or invalid. Confirm the credential is properly configured.
- Network or API rate limit issues can cause failures. Check network connectivity and Autotask API usage limits.