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 Milestone in the Autotask system. It allows users to specify the milestone by its ID and update various fields of the milestone using a flexible field mapping mechanism. This is useful for automating contract management workflows where milestone details need to be programmatically modified, such as adjusting milestone dates, statuses, or descriptions based on external triggers or data changes.
Properties
| Name | Meaning |
|---|---|
| Milestone ID | The unique identifier of the contract milestone to update. This is required to specify which milestone record will be modified. |
| Fields | A resource mapper input that defines which fields of the contract milestone should be updated and their new values. This allows selective updating of milestone properties. |
Output
JSON
id- The ID of the updated contract milestone.fields- The updated fields and their new values for the contract milestone.status- The status or result of the update operation, indicating success or failure.
Dependencies
- Requires an API key credential for authenticating with the Autotask REST API.
Troubleshooting
- If the Milestone ID is missing or invalid, the node will fail to locate the milestone to update. Ensure the ID is correct and exists in Autotask.
- Incorrect or unsupported field names in the Fields mapping may cause the update to fail. Verify field names against the Autotask contract milestone schema.
- API authentication errors may occur if the API key credential is invalid or expired. Re-authenticate or update credentials as needed.
- Network or API rate limiting issues can cause intermittent failures. Implement retry logic or check API usage limits.