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 multiple Contract Milestone records from the Autotask system. It is useful for workflows that need to fetch a list of contract milestones, for example, to display milestone progress, generate reports, or synchronize contract milestone data with other systems. Users can specify which fields to retrieve, limit the number of records, and choose whether to include human-readable labels for picklist and reference fields.
Properties
| Name | Meaning |
|---|---|
| Fields | Defines which fields of the Contract Milestone resource to retrieve and map in the output. Supports custom mapping and selection of specific fields. |
| Get All | Boolean flag to determine whether to return all matching Contract Milestone records or limit the results. |
| Max Records | Specifies the maximum number of Contract Milestone records to return when 'Get All' is false. The value must be between 1 and 500. |
| Add Picklist Labels | Determines whether to add additional fields with human-readable labels for picklist fields in the output. Labels are added only for non-empty values. |
| Add Reference Labels | Determines whether to add additional fields with human-readable labels for reference fields in the output. Labels are added only for non-empty values. |
| Select Columns Names or IDs. | Allows selection of specific fields (columns) to include in the response. If no fields are selected, all fields are returned. The ID field is always included. |
| Flatten User-Defined Fields | If enabled, user-defined fields (UDFs) are moved to the top level of each returned object instead of being nested inside a userDefinedFields array. |
Output
JSON
id- Unique identifier of the Contract Milestone record.fields*- Selected fields of the Contract Milestone as specified by the user, including standard and user-defined fields.
*_label- Optional human-readable labels for picklist and reference fields, added if enabled in the node properties.
Dependencies
- Requires an API key credential for Autotask REST API authentication.
Troubleshooting
- If no records are returned, verify that the Contract Milestone resource exists and that the query parameters (fields, filters) are correct.
- If the node returns an authentication error, check that the Autotask API credentials are valid and have sufficient permissions.
- If the maximum records limit is exceeded, reduce the 'Max Records' value or enable 'Get All' to fetch all records.
- If picklist or reference labels are missing, ensure that 'Add Picklist Labels' and 'Add Reference Labels' options are enabled and that the fields have non-empty values.