Short answer: Drop the "Asana → Search 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 |
|---|---|---|---|
Workspace GID workspace | string | Required | Asana workspace GID — a numeric global ID. Find via List Workspaces. |
Search Text text | string | Optional | Search Text. Example: homepage redesign |
Completed completed | options | Optional | Completed. Options: Any, Incomplete only, Complete only |
Assignee GID assignee_any | string | Optional | Assignee GID. Example: 456 |
Project GID projects_any | string | Optional | Project GID. Example: 789 |
{"workspace": "e.g. 1234567890","text": "e.g. homepage redesign","completed": "{{trigger.completed}}","assignee_any": "e.g. 456","projects_any": "e.g. 789"}
{"data": [{"gid": "123","name": "Homepage redesign","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.