CompleteProjectTasksAction
Marks project tasks as completed. Each request supplies a list of project task ids and returns one result, index-aligned to the requests, reporting whether every task completed, or the tasks that failed with a reason for each. All ids across every request are validated and committed as a single all-or-none batch: If any ID is missing, inaccessible, not a valid project task ID, or fails a completion rule, none of the Project Tasks are completed even if not mentioned in the Failed Task IDs. If there are any failed project task IDs the agent will treat the whole request as unsuccessful, and not report any project task as completed.
| Property | Value |
| Label | Complete Project Tasks |
| Category | Project Task Management |
| Since | Summer 2026 |
| Read-only | No |
| Supports Agents | Yes |
| Supports Flows | Yes |
| Async Action | No |
| Keywords | finish, mark done |
Request Parameters
| Field | Type | Label | Description | Required |
projectTaskIds | List<Id> | Project Task IDs | The IDs of the project tasks to mark as completed. | Yes |
Response Parameters
| Field | Type | Label | Description | Required |
isSuccess | Boolean | Is Success | True only if every task in this request completed. False if any task failed, including a failure in another request, since all requests commit as one. | No |
failedTaskIds | List<Id> | Failed Task IDs | The IDs from this request that were not completed, each index-aligned to an Error Messages entry. Populated only when Is Success is false. Any ID absent from this list has not necessarily completed, so use Is Success to determine the outcome. | No |
errorMessages | List<String> | Error Messages | The reason each failed task was not completed; index-aligned to Failed Task Ids. Any IDs here mean that all tasks in the request have not completed, so ensure to inform the user of that. | No |
|