List Workspaces: 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
Fields opt_fields	string	Optional	Comma-separated field names to include

Sample request

{
  "opt_fields": "e.g. name,is_organization"
}

Returns

{
  "data": [
    {
      "gid": "123456",
      "name": "Acme Corp",
      "is_organization": true
    },
    {
      "gid": "789012",
      "name": "Personal Projects",
      "is_organization": false
    }
  ]
}

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

FAQ

Questions about List Workspaces.

What does the List Workspaces action do in Asana?

Lists all workspaces accessible to the authenticated Asana user. Required first step for any cross-workspace automation.

What inputs does List Workspaces require?

List Workspaces has no required inputs. Sensible defaults are applied if you leave fields blank.

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 Workspaces support batch operations?

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