Asana ACTION
Search Tasks Premium
Searches for a task by name, assignee, section, project, completed since, and modified since. Requires a Premium Asana account. See the documentation
- Action
- Read only
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Asana account once, then configure and run Search Tasks Premium from your backend or agent.
SCHEMA
Inputs
Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.
| Property | Type | Description |
|---|---|---|
workspace Workspace | string | Gid of a workspace. Required Dynamic |
project Project | string | List of projects. This field uses the project GID. Optional Dynamic |
name Name | string | The task name to search for Optional |
assignee Assignee | string | The assignee to filter tasks on Optional Dynamic |
section Section | string | Section GID used to filter tasks (for example: 1200123456789013). Provide project so valid section IDs can be resolved. Optional Dynamic |
completedSince Completed Since | string | Only return tasks that are either incomplete or completed since this time. ISO 8601 format (for example: 2026-04-14 or 2026-04-14T00:00:00Z). Optional |
modifiedSince Modified Since | string | Only return tasks modified since this time. ISO 8601 format (for example: 2026-04-14 or 2026-04-14T00:00:00Z). Optional |
maxResults Max Results | integer | The maximum total number of results to return across all paginated API calls. Each page fetches up to 100 items (Asana's maximum); this cap is applied after auto-pagination completes. Optional |
REFERENCE
Tool details
Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.
- Registry key
- asana-search-tasks-premium
- Version
- 0.0.5
- App
- Asana
- Authentication
- OAuth
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗