Wrike
Manage Wrike tasks, folders/projects, comments, contacts and timelogs.
About
Wrike ships in the w6w first-party pack. It declares 29 actions, 3 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.wrike- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Project Management · Productivity
Overview
Wrike is a work-management platform organized around a folder tree: spaces contain projects and folders, which contain tasks, which carry comments, timelogs and attachments. This app covers that core surface end to end — creating, searching, updating and deleting tasks and folders/projects, reading and posting comments, reading and updating contacts (Wrike’s term for users and groups), and recording or editing timelogs — plus read access to attachment metadata and download links.
Wrike’s API v4 is unusual among REST APIs: every mutating request (POST/PUT) passes its whole payload as query-string parameters, not a JSON body, with arrays and objects JSON-encoded inline inside the query value. Every action in this app builds requests that way, matching Wrike’s own OpenAPI definitions rather than the more common JSON-body convention. Wrike also serves customer data from one of three fixed regional hosts (US, EU, US2); the Connection records which one, and every action reads it from there rather than guessing.
Health checks track credential liveness via Wrike’s lightweight, scope-free /version endpoint and the connected account’s own suspension flag. Wrike publishes no machine-readable status feed and no rate-limit headroom, and both are declared as such rather than guessed at.
Build with Wrike
Three routes to the same 29 actions. The Workflow tab is generated from Wrike's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Get Account
account-get Fetch the current account's settings, root/Recycle Bin folder IDs and subscription.
Get Attachment Download URL
attachment-download-url-get Get a public download link for an attachment. Valid for 24 hours from the time of this call.
Update Comment
comment-update Edit a comment's text. Only possible within 5 minutes of the comment's creation — a hard Wrike platform limit.
Update Contact
contact-update Update the requesting user's own contact record (or, for an admin, a group's info by group ID). Cannot update another user's contact — see Wrike's separate, admin-only 'Modify User' endpoint for that, which this app does not implement.
Create Folder
folder-create Create a folder — or a project, when `project` is set — within another folder.
Delete Folder
folder-delete Move a folder and its descendant folders/tasks to the Recycle Bin, unless they have parents outside the deleted subtree.
Update Folder
folder-update Update a folder/project's title, description, parents, sharing or project settings.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Wrike's real ids.
{
"manifestVersion": "2",
"name": "wrike-example",
"steps": [
{
"id": "attachment-download-url-get",
"uses": {
"app": "io.w6w.wrike",
"action": "attachment-download-url-get",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"attachmentId": "<attachmentId>"
}
}
]
}Here are some of the things you can do
-
Get Attachment Download URL
readattachment-download-url-get -
Get Account
readaccount-get -
Get Attachments by ID
readattachment-get -
List Task Attachments
searchattachment-list -
Create Comment
performcomment-create
+24 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Wrike, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Wrike. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "attachment-download-url-get",
payload: {
attachmentId: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action attachment-download-url-get --payload '{"attachmentId":"<value>"}'Give an AI agent Wrike — without giving it Wrike's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.wrike#attachment-download-url-get",
"input": {
"attachmentId": "<attachmentId>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Wrike connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Wrike's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Wrike itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Wrike declares its own checks, so its health is a property of the app rather than something the host guesses at.
Wrike platform status
API request-rate headroom
Account subscription usable
GET /account's subscription.suspended flag. A suspended account fails every action regardless of token validity, which is a different problem than an expired token.