Update Task

google_tasks.update_task
ActionBusiness appsconnection required

Calls the Google Tasks API PATCH /lists/{tasklist}/tasks/{task}.

Change a task's title, notes, due date or status.

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

6 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
task_id
Task id. Supports {{ }}.
stringYes———
tasklist
Task list id.
stringNo@default——
title
New title. Left blank, the title is unchanged.
stringNo———
notes
New notes. Left blank, the notes are unchanged.
stringNo———
due
New due date (RFC3339).
stringNo———
status
'completed' marks the task done; 'needsAction' re-opens it.
stringNo—one of "needsAction", "completed"—
  • At least one of title, notes, due, status must be set.

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "tasklist": "@default"
}

Output

One shape.

result

FieldTypeExample
ok
boolean—
id
string—
title
string—
status
string—
due
string—
notes
string—
completed
string—
web_view_link
string—
task
The task as it now stands: 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": "",
  "due": "",
  "id": "",
  "notes": "",
  "ok": false,
  "status": "",
  "task": {},
  "title": "",
  "web_view_link": ""
}

See Update 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.