Wrike ACTION
Update Folder
Update a folder or project's metadata via PUT /folders/{folderId}. Supply the optional 'project' prop to set project attributes (or null to convert a project back to a folder); there is no separate update-project action. Use List Folder ID Options to obtain the folderId. 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 Folder 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-folder",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
wrike: { authProvisionId: "apn_xxxxxxx" },
folderId: "Folder 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-folder",
"configured_props": {
"wrike": { "authProvisionId": "apn_xxxxxxx" },
"folderId": "Folder 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-folder",
arguments: {
folderId: "Folder 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 |
|---|---|---|
folderId Folder ID | string | The ID of the folder or project to update, e.g. IEAASDF3. Run List Folder ID Options to look up IDs. Required |
title Title | string | New folder/project title. Optional |
description Description | string | New folder/project description. Optional |
project Project | string | JSON object of project attributes. Example: {"status":"Yellow"}. Status is one of Red, OnHold, Yellow, Completed, Custom, Cancelled, Green. Send JSON null to convert a project back into a plain folder. Optional |
addParents Add Parents | string[] | Folder IDs to add as parents. Run List Folder ID Options to look up IDs. Optional |
removeParents Remove Parents | string[] | Folder IDs to remove as parents. Optional |
customFields Custom Fields | string | JSON array of custom field objects. Example: [{"id":"IEAASDF3JQAAAAAA","value":"Q3"}]. 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-folder
- Version
- 0.0.2
- App
- Wrike
- Authentication
- OAuth
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗