Wrike ACTION
Update Task
Update any combination of a Wrike task's fields (title, description, status, importance, assignees, dates, custom fields) in a single call via PUT /tasks/{taskId}. Supersedes the former Update Task Custom Fields action. Use Find Tasks or Get Task to obtain the taskId; use List Contact ID Options for assignee IDs and List Custom Fields Keys Options for custom field IDs. See the documentation
- Action
- Writes data
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Wrike account once, then configure and run Update Task 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-update-task",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
wrike: { authProvisionId: "apn_xxxxxxx" },
taskId: "Task ID",
title: "Title",
},
})
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-update-task",
"configured_props": {
"wrike": { "authProvisionId": "apn_xxxxxxx" },
"taskId": "Task ID",
"title": "Title"
}
}'// 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-update-task",
arguments: {
taskId: "Task ID",
title: "Title",
},
})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 |
|---|---|---|
taskId Task ID | string | The ID of the task to update, e.g. IEAASDF3KQAAAAAA. Run the Find Tasks action to look up task IDs. Required |
title Title | string | New task title. Optional |
description Description | string | New task description. Optional |
status Status | string | New task status. One of: Active, Deferred, Completed, Cancelled. Optional |
importance Importance | string | New task importance. One of: High, Normal, Low. Optional |
addResponsibles Add Responsibles | string[] | Contact IDs to add as assignees, e.g. KUABCDEF (the intake 'responsibles' input maps here; Wrike PUT has no flat responsibles field). Run List Contact ID Options to look up IDs. Optional |
removeResponsibles Remove Responsibles | string[] | Contact IDs to remove as assignees. Run List Contact ID Options to look up IDs. Optional |
dates Dates | string | JSON object of task dates. Example: {"start":"2026-07-23","due":"2026-09-30","type":"Planned"}. Optional |
customStatus Custom Status | string | ID of a custom workflow status to set. Optional |
customFields Custom Fields | string | JSON array of custom field objects to set. Example: [{"id":"IEAASDF3JQAAAAAA","value":"Done"}]. Run List Custom Fields Keys Options to discover valid field IDs. 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-update-task
- Version
- 0.0.2
- App
- Wrike
- Authentication
- OAuth
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗