Add Task to Section
asana.add_task_to_section
ActionBusiness appsconnection required
Calls the Asana API with the connection's credentials.
Move a task into a section of the project that owns it.
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
4 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 |
|---|---|---|---|---|---|
section_gid The section's gid. | string | Yes | — | — | — |
task The task gid to move. | string | Yes | — | — | — |
insert_before Place the task before this task gid within the section. | string | No | — | — | — |
insert_after Place the task after this task gid within the section. | string | No | — | — | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
ok True when Asana accepted the move. | boolean | — |
section_gid The section the task was moved into. | string | — |
task_gid The task that was moved. | string | — |
{
"ok": false,
"section_gid": "",
"task_gid": ""
}See Add Task to Section 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.