List Projects: 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
Workspace GID workspace	string	Required	Asana workspace GID — a numeric global ID. Find via List Workspaces.
Include Archived archived	options	Optional	Include Archived. Options: No, Yes
Fields opt_fields	string	Optional	Fields. Example: name,owner,due_date,color

Sample request

{
  "workspace": "e.g. 1234567890",
  "archived": "{{trigger.archived}}",
  "opt_fields": "e.g. name,owner,due_date,color"
}

Returns

{
  "data": [
    {
      "gid": "123",
      "name": "Marketing Q1",
      "owner": {
        "gid": "456",
        "name": "John"
      }
    }
  ]
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about List Projects.

What does the List Projects action do in Asana?

Lists projects in an Asana workspace, optionally scoped to a team. The standard first step for any flow that needs a project_gid.

What inputs does List Projects require?

Required: Workspace 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 Projects support batch operations?

Yes. Run List Projects 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