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 enables users to create a new Project Phase within the Autotask system via its REST API. It is useful for project management automation where phases of a project need to be programmatically added, such as when setting up new projects or updating project workflows. For example, a user can automate the creation of project phases like 'Planning', 'Execution', and 'Closure' based on predefined templates or triggers in their workflow.
Properties
| Name | Meaning |
|---|---|
| Fields | Defines the specific fields and their values to set when creating the Project Phase. This property uses a resource mapper to allow users to map input data to the appropriate fields of the Project Phase resource. |
Output
JSON
id- The unique identifier of the newly created Project Phase.name- The name of the Project Phase as created.startDate- The start date of the Project Phase.endDate- The end date of the Project Phase.status- The current status of the Project Phase.additionalProperties- Any other fields returned by the Autotask API related to the created Project Phase.
Dependencies
- Requires an Autotask API credential (API key or token) to authenticate requests to the Autotask REST API.
Troubleshooting
- If the node fails with authentication errors, verify that the Autotask API credentials are correctly configured and have sufficient permissions.
- Validation errors may occur if required fields for the Project Phase are missing or incorrectly mapped; ensure all mandatory fields are provided.
- Network or API errors can happen if the Autotask service is unreachable; check network connectivity and Autotask service status.
- If the resource or operation is not supported error appears, confirm that the node's resource is set to 'phase' and operation to 'create'.