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 retrieves detailed information about a specific Contract Milestone from the Autotask system using its unique Milestone ID. It is useful for workflows that need to fetch milestone data for contracts, such as tracking project progress, billing milestones, or integrating contract milestone details into other systems. For example, a user can automate the retrieval of milestone status and details to update project management dashboards or trigger notifications when a milestone is reached.
Properties
| Name | Meaning |
|---|---|
| Milestone ID | The unique identifier of the contract milestone to retrieve. This is a required field to specify which milestone's data to fetch. |
| Add Picklist Labels | Determines whether to automatically add human-readable label fields (with a '_label' suffix) for picklist fields in the response. Labels are only added if the picklist field has a value. |
| Add Reference Labels | Determines whether to automatically add human-readable label fields (with a '_label' suffix) for reference fields in the response. Labels are only added if the reference field has a value. |
| Select Columns Names or IDs. | Allows selection of specific fields to include in the response. If no fields are selected, all fields are returned. The ID field is always included regardless of selection. |
| Flatten User-Defined Fields | If enabled, user-defined fields (UDFs) are brought up to the top level of the returned object instead of being nested inside a 'userDefinedFields' array, simplifying access to these fields. |
Output
JSON
id- The unique identifier of the contract milestone.name- The name or title of the contract milestone.description- Detailed description of the milestone.status- Current status of the milestone.startDate- The start date of the milestone.endDate- The end date or due date of the milestone.userDefinedFields- An array of user-defined fields related to the milestone, unless flattened to top-level properties.
_label - Human-readable labels for picklist or reference fields, added automatically if enabled.
Dependencies
- Requires an API key credential for Autotask REST API authentication.
Troubleshooting
- If the Milestone ID is missing or invalid, the node will throw an error indicating the milestone could not be found. Ensure the ID is correct and exists in Autotask.
- If API authentication fails, verify that the API key credential is correctly configured and has sufficient permissions.
- Selecting specific columns that do not exist or are misspelled may result in incomplete data or errors. Use the provided dropdown or load options to select valid fields.
- Enabling 'Flatten User-Defined Fields' may cause naming conflicts if UDF names overlap with standard fields; use with caution.