Asana ACTION
Search Tasks
Searches for Asana tasks by name within a project, section, or by assignee. Must specify exactly one of:
project, section, or assignee (project + section together is also valid). The name filter is a client-side substring match applied after fetching. For cross-project full-text search, use Search Tasks Premium instead. Returns task records with gid and name (plus any requested optFields). Example: call with workspace: '1200123456789012', project: '1204567890123456', name: 'Q3' → returns tasks in that project whose names contain 'Q3'. 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 from your backend or agent.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "asana-search-tasks",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
asana: { authProvisionId: "apn_xxxxxxx" },
workspace: "Workspace",
project: "Project",
},
})
console.log(result)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "asana-search-tasks",
"configured_props": {
"asana": { "authProvisionId": "apn_xxxxxxx" },
"workspace": "Workspace",
"project": "Project"
}
}'// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "asana",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
name: "asana-search-tasks",
arguments: {
workspace: "Workspace",
project: "Project",
},
})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 the workspace, e.g. 1200123456789012. Use List Workspaces to find available workspace GIDs. Required |
project Project | string | List of projects. This field uses the project GID (e.g. 1204567890123456). Use Search Projects to find available project GIDs (the gid field). Optional |
name Name | string | The task name to search for (client-side substring match). If omitted, all tasks matching the other filters are returned, e.g. Q3 report. Optional |
assignee Assignee | string | List of users. This field uses the user gid (e.g. 1198765432109876). Use the List Users action to retrieve available user GIDs. Optional |
section Section | string | The section GID to filter tasks on, e.g. 1203456789012345. Use Search Sections with a project GID to find available section GIDs. Optional |
completedSince Completed Since | string | Only return tasks that are either incomplete or that have been completed since this time. ISO 8601 date string Optional |
modifiedSince Modified Since | string | Only return tasks that have been modified since the given time. ISO 8601 date string Optional |
optFields Opt Fields | string[] | Optional task properties to include in the response (e.g. created_at, due_on, custom_fields). Nested paths are allowed; gid is always returned. See the documentation 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
- Version
- 0.5.1
- App
- Asana
- Authentication
- OAuth
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗