Short answer: Drop the "Asana → Get Project" 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 |
|---|---|---|---|
Project GID project_gid | string | Required | Asana project GID — a numeric global ID. Find via List Projects. |
Fields opt_fields | string | Optional | Comma-separated field names to include |
{"project_gid": "e.g. 1234567890","opt_fields": "e.g. name,owner,due_date,color,members"}
{"data": {"gid": "1234567890","name": "Marketing Q1","color": "light-green","owner": {"gid": "456","name": "John"},"archived": false,"due_date": "2025-03-31","permalink_url": "https://app.asana.com/0/1234567890"}}
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.