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 updates an existing Project Phase in the Autotask system by specifying the Phase ID and the fields to update. It is useful for managing project phases dynamically within workflows, such as modifying phase details like name, status, or dates based on external triggers or data changes.
Properties
| Name | Meaning |
|---|---|
| Phase ID | The unique identifier of the project phase to update. This is required to specify which phase record will be modified. |
| Fields | A resource mapper input that defines which fields of the project phase should be updated and their new values. It supports defining fields manually or using auto-mapping features to map data dynamically. |
Output
JSON
id- The ID of the updated project phase, confirming which phase was modified.fields- The updated fields and their new values after the update operation.status- The status of the update operation, indicating success or failure.message- Additional information or error messages related to the update operation.
Dependencies
- Requires an API key credential for authenticating with the Autotask REST API.
- Depends on the Autotask REST API endpoint for project phases.
Troubleshooting
- If the Phase ID is invalid or does not exist, the node will throw an error indicating the phase was not found. Verify the ID before running the node.
- Incorrect or incomplete field mappings can cause the update to fail or partially apply. Ensure all required fields for the update are correctly mapped.
- Authentication errors may occur if the API key credential is missing or invalid. Confirm the credential configuration in n8n.
- Network or API rate limit issues can cause failures; retry or check API usage limits if errors occur.