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 retrieve detailed information about a specific project phase within a project management context. It is designed to fetch data for a given project phase by specifying the project ID and the phase ID. This is useful for workflows that need to access or manipulate project phase details, such as tracking progress, updating phase information, or integrating project phase data with other systems.
Properties
| Name | Meaning |
|---|---|
| Project ID | The unique identifier of the project to which the phase belongs. This is required to scope the phase retrieval to the correct project. |
| Phase ID | The unique identifier of the specific phase within the project to retrieve. This is required to identify the exact phase. |
| Add Picklist Labels | Determines whether to automatically add human-readable '_label' fields for picklist fields in the response. Labels are only added if the picklist fields have non-empty values. |
| Add Reference Labels | Determines whether to automatically add human-readable '_label' fields for reference fields in the response. Labels are only added if the reference fields have non-empty values. |
| 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 | Determines whether user-defined fields (UDFs) should be brought up to the top level of each returned object instead of being nested inside a 'userDefinedFields' array. |
Output
JSON
id- The unique identifier of the project phase.projectID- The ID of the project to which this phase belongs.name- The name of the project phase.startDate- The start date of the project phase.endDate- The end date of the project phase.status- The current status of the project phase.userDefinedFields- An array of user-defined fields associated with the phase, unless flattened to top-level properties.
_label - Human-readable labels for picklist or reference fields, added automatically if enabled and values are present.
Dependencies
- Requires an API key credential for authenticating with the Autotask REST API.
Troubleshooting
- If the node returns an error indicating the project or phase ID is invalid, verify that the IDs are correct and exist in the Autotask system.
- If no data is returned, check that the API credentials have sufficient permissions to access project phase data.
- Errors related to missing fields may occur if 'Select Columns' are specified incorrectly; ensure field names or IDs are valid.
- If labels are not appearing as expected, verify that 'Add Picklist Labels' and 'Add Reference Labels' options are enabled and that the fields have non-empty values.