Short answer: Drop the "Asana → List Tags" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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. |
Page Size limit | string | Optional | How many results per page (1-100) |
{"workspace": "e.g. 1234567890","limit": "e.g. 50"}
{"data": [{"gid": "1234567890","name": "Urgent","resource_type": "tag"}]}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.