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 task in the Autotask system by specifying the task's unique ID and the fields to modify. It is useful for automating task management workflows, such as updating task status, priority, or other attributes programmatically. For example, it can be used to update a task's due date or assign it to a different user based on external triggers or conditions.
Properties
| Name | Meaning |
|---|---|
| Task ID | The unique identifier of the project task to update. |
| Fields | The set of fields and their new values to update on the specified task. This uses a resource mapper to define which fields to modify. |
Output
JSON
id- The unique identifier of the updated project task.fields- The updated fields and their values after the update operation.status- The status of the update operation, e.g., success or failure.message- Additional information or error message if the update failed.
Dependencies
- Requires an Autotask API key credential for authentication to access the Autotask REST API.
Troubleshooting
- If the Task ID is invalid or does not exist, the node will throw an error indicating the task was not found. Verify the Task ID is correct.
- If required fields are missing or invalid in the 'Fields' property, the update may fail with validation errors. Ensure all mandatory fields are provided and correctly formatted.
- Authentication errors may occur if the API key credential is missing or invalid. Confirm the credential is configured properly in n8n.
- Network or API rate limit errors can cause failures. Check network connectivity and Autotask API usage limits.