Move Task

google_tasks.move_task
ActionBusiness appsconnection required

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

Make a task a subtask, or move it within its list.

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

4 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——
parent
Task id to nest under. Blank promotes the task to top level.
stringNo———
previous
Place the task directly after this sibling task id.
stringNo———

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—
parent
The task's parent after the move, if any.
string—
position
Sort position within its level.
string—
task
The moved 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—
{
  "id": "",
  "ok": false,
  "parent": "",
  "position": "",
  "task": {}
}

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