ActionAsanaUpdated September 2026
How do I list sections in an Asana project?
Short answer: You can list sections in Asana by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Asana List Sections action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Inputs
The fields this action accepts.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Project GID project_gid | string | Required | Asana project GID — a numeric global ID. Find via List Projects. |
Sample request
{"project_gid": "e.g. 1234567890"}
Returns
{"data": [{"gid": "sec123","name": "To Do"},{"gid": "sec456","name": "In Progress"},{"gid": "sec789","name": "Done"}]}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for List Sections.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about List Sections.
What does the List Sections action do in Asana?
Lists sections in an Asana project with their names and order. Used to populate a section picker before creating or moving a task.
What inputs does List Sections require?
Required: Project GID. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Asana returns an error?
The run history shows the failed step with its input and the error message Asana returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does List Sections support batch operations?
Run List Sections inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Asana's rate limits.
More actions
Other Asana actions.
Action
Add Comment
Adds a comment (story) to an Asana task. Used for automation activity logs, AI summary notes, or status broadcasts.
ActionAdd Tag to Task
Adds an existing tag to an Asana task. Used to tag based on AI classification or to auto-categorize incoming tasks.
ActionCreate Section
Creates a new section in an Asana project. Sections organize the task list (or columns in board view); useful for templated project scaffolding.
ActionCreate Subtask
Creates a subtask under an existing Asana task with name, assignee, due date, and notes. Used for templated work breakdowns.
ActionCreate Task
Creates a new task in an Asana project with name, notes, assignee, due date, section, tags, and custom fields. The standard write action for piping forms or external tickets into Asana.
ActionDelete Task
Deletes a task from Asana by GID. Moves to trash for 30 days before permanent deletion.