Short answer: Drop the "Asana → List Tasks" 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 | string | Required | Project GID. Example: 1234567890 |
Completed Since completed_since | string | Optional | Only return tasks completed after this ISO 8601 date. Use 'now' for incomplete tasks only. |
Fields opt_fields | string | Optional | Comma-separated field names to include |
{"project": "e.g. 1234567890","completed_since": "e.g. now","opt_fields": "e.g. name,assignee,due_on,completed"}
{"data": [{"gid": "12345","name": "Task 1","completed": false}]}
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.