Set Task Parent
asana.set_task_parent
ActionBusiness appsconnection required
Calls the Asana API with the connection's credentials.
Make a task a subtask of another task, or move it between parents.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- Bearer token
- Providers
- Asana
- Secret shape
- the Asana personal access token, or {"token": "…"}
- Resolved by
- config.connection_id, else node.connection_id
Configuration
5 fields, 2 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_gid The task's gid. | string | Yes | — | — | — |
parent The task gid to become the parent. | string | Yes | — | — | — |
insert_after Place this subtask after the given sibling subtask gid. | string | No | — | — | — |
insert_before Place this subtask before the given sibling subtask gid. | string | No | — | — | — |
opt_fields Comma-separated extra fields to return, e.g. 'name,completed,due_on,assignee.name'. Asana returns a thin default set without it. | string | No | — | — | — |
Output
One shape.
result
The provider's response object, as returned.
Extra keys beyond the ones listed can appear.
{}See Set Task Parent run in a workflow.
In a technical demo we add the Asana connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.