Wrike ACTION
Find Tasks
Query tasks within a Wrike folder or project via GET /folders/{folderId}/tasks, with optional status, due-date, importance, and assignee filters. Answers questions like 'what's overdue in the Marketing project?'. Use List Folder ID Options to obtain a folderId. Use the returned task IDs with Get Task or Update Task. See the documentation
- Action
- Read only
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Wrike account once, then configure and run Find 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: "wrike-find-tasks",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
wrike: { authProvisionId: "apn_xxxxxxx" },
folderId: "Folder ID",
status: ["Status"],
},
})
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": "wrike-find-tasks",
"configured_props": {
"wrike": { "authProvisionId": "apn_xxxxxxx" },
"folderId": "Folder ID",
"status": ["Status"]
}
}'// 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": "wrike",
},
},
},
)
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: "wrike-find-tasks",
arguments: {
folderId: "Folder ID",
status: ["Status"],
},
})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 |
|---|---|---|
folderId Folder ID | string | The ID of the folder or project whose tasks to query, e.g. IEAASDF3. Run the List Folder ID Options action to look up folder IDs. Required |
status Status | string[] | Filter by task status. One or more of: Active, Deferred, Completed, Cancelled. Optional |
importance Importance | string | Filter by task importance. One of: High, Normal, Low. Optional |
dueDateGt Due Date From | string | Return tasks due on or after this date (maps to dueDate.start). Format yyyy-MM-dd, e.g. 2026-07-01. Optional |
dueDateLt Due Date To | string | Return tasks due on or before this date (maps to dueDate.end). Format yyyy-MM-dd, e.g. 2026-08-01. Optional |
responsibles Responsibles | string[] | Filter by assignee contact IDs, e.g. KUABCDEF. Run the List Contact ID Options action to look up contact IDs. Optional |
limit Limit | integer | Maximum number of tasks to return. Min 1, max 1000. Defaults to 100. 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
- wrike-find-tasks
- Version
- 0.0.2
- App
- Wrike
- Authentication
- OAuth
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗