Complete Task
google_tasks.complete_task
ActionBusiness appsconnection required
Calls PATCH /lists/{tasklist}/tasks/{task} with status=completed.
Mark a Google Task as completed.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- OAuth 2.0
- Providers
- Google Tasks
- Secret shape
- {"client_id", "client_secret", "refresh_token"}
- Resolved by
- config.connection_id, else node.connection_id
Configuration
2 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
task_id Task id. Supports {{ }}. | string | Yes | — | — | — |
tasklist Task list id. | string | No | @default | — | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"tasklist": "@default"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
ok | boolean | — |
id | string | — |
title | string | — |
status 'completed'. | string | — |
completed When Google recorded the completion. | string | — |
web_view_link | string | — |
task The completed task: id, title, status ('needsAction' or 'completed'), due, notes, updated, completed, parent (set on a subtask), position, web_view_link, self_link, deleted, hidden, links[{type, description, link}]. | object | — |
{
"completed": "",
"id": "",
"ok": false,
"status": "",
"task": {},
"title": "",
"web_view_link": ""
}Related Google Tasks nodes
See Complete Task run in a workflow.
In a technical demo we add the Google Tasks connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.