AsanaSearch tasks
BetaReads data
Searches a whole Asana workspace by text, assignee, project and dates.
Settings
| Setting | What it is |
|---|---|
| ConnectionRequired | The Asana connection the step signs in with. |
| Workspace idRequired | The workspace to search — search is per workspace. |
| Text | text |
| Assignee | One person's tasks — an id or e-mail, or the word me. |
| Projects | Comma-separated project ids to search inside. |
| Completed | true/false |
| Sort by | "due_date" or "created_at" or "completed_at" or "likes" or "modified_at" |
| Tasks per call | 1 to 100. Asana's search cannot be paged: this returns at most 100 tasks, the newest first — narrow the search if you need more. |
| Fields to fetch | Asana leaves out anything you do not ask for. Add a field here to get it back. |
Technical details
| Key | Value |
|---|---|
connection | texta connection id from `requires.connections` (provider `asana`) |
workspaceId | text |
text | text |
assigneeAny | text |
projectIds | text |
completed | true/false |
sortBy | "due_date" or "created_at" or "completed_at" or "likes" or "modified_at", by default "modified_at" |
limit | number, by default 100 |
fields | text, by default "gid,name,completed,assignee,due_on,projects" |
Output
| Field | Type |
|---|---|
tasks | array |
taskCountTasks in this answer | number |
Sample output, and the expression for each field
- taskCount0
- tasks[]
Errors
When a step of this node stops a run, the run page shows a code. Look it up:
Example step
The step as a flow file holds it. Replace each value in <…>.
{
"config": {
"assigneeAny": "",
"connection": "<connection id>",
"fields": "gid,name,completed,assignee,due_on,projects",
"limit": 100,
"projectIds": "",
"sortBy": "modified_at",
"text": "",
"workspaceId": "<workspace id>"
},
"label": "Search tasks",
"type": "asana.searchTasks",
"version": 1
}