List Sections
asana.list_sections
ActionBusiness appsconnection required
Calls the Asana API with the connection's credentials.
List the sections of a project in board order.
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, 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 |
|---|---|---|---|---|---|
project_gid The project's gid. | string | Yes | — | — | — |
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 | — | — | — |
limit Maximum records to return in this page. Asana caps a page at 100. | number | No | — | 1–100 | — |
offset Pagination token from a previous call's 'next_offset'. Asana's offsets are opaque tokens, not row numbers. | string | No | — | — | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
items The records Asana returned for this page. | array | — |
count How many records this page contains. | number | — |
next_offset Pagination token for the next page, or null when this is the last page. | string | — |
{
"count": 0,
"items": [],
"next_offset": ""
}See List Sections 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.