List Sections: Asana action

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.

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 workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does List Sections support batch operations?

Yes. Run List Sections inside a Loop node to process arrays. Tiny Command handles Asana's rate limits automatically so you don't have to throttle manually.

More actions