| name | wrike |
| description | Manage Wrike tasks, projects, folders, and comments via the Wrike REST API. |
| metadata | {"openclaw":{"emoji":"📋","requires":{"bins":["claw-wrike"],"env":["WRIKE_TOKEN"]},"primaryEnv":"WRIKE_TOKEN","install":[{"id":"npm","kind":"node","package":"claw-wrike","bins":["claw-wrike"],"label":"Install claw-wrike (npm)"}]}} |
Wrike CLI
Manage Wrike tasks, projects, folders, and comments. All commands return JSON: {"ok": true, "data": ...} on success, {"ok": false, "error": "..."} on failure.
Setup
claw-wrike config set --token <WRIKE_TOKEN>
Quick Reference
claw-wrike <entity> <command> [--flags]
Account & Spaces
claw-wrike account
claw-wrike space list
claw-wrike space get --id <id>
Folders & Projects
Wrike treats folders and projects as the same entity. Projects are folders with extra properties (owners, dates, status).
claw-wrike folder list
claw-wrike folder list --space <id>
claw-wrike folder list --parent <id>
claw-wrike folder get --id <id>
claw-wrike folder create --parent <id> --title "Folder name"
claw-wrike folder create --parent <id> --title "Project name" --project
claw-wrike folder create --parent <id> --title "Project name" --project --owner <contactId> --start-date 2026-03-01 --end-date 2026-06-01
claw-wrike folder create --parent <id> --title "Folder name" --dry-run
claw-wrike folder update --id <id> --title "New title"
claw-wrike folder update --id <id> --description "New description"
claw-wrike folder update --id <id> --add-parent <folderId>
claw-wrike folder update --id <id> --remove-parent <folderId>
claw-wrike folder update --id <id> --dry-run
claw-wrike folder delete --id <id>
claw-wrike folder delete --id <id> --dry-run
Tasks
claw-wrike task list
claw-wrike task list --folder <id>
claw-wrike task list --space <id>
claw-wrike task list --status Active
claw-wrike task list --assignee "Jane"
claw-wrike task list --importance High
claw-wrike task list --limit 20
claw-wrike task get --id <id>
claw-wrike task create --folder <id> --title "Task name"
claw-wrike task create --folder <id> --title "Task name" --assignee "Jane" --due 2026-03-01 --importance High
claw-wrike task create --folder <id> --title "Task name" --dry-run
claw-wrike task update --id <id> --title "New title"
claw-wrike task update --id <id> --add-assignee "Jane"
claw-wrike task update --id <id> --remove-assignee "Jane"
claw-wrike task update --id <id> --due 2026-04-01 --importance Low
claw-wrike task update --id <id> --status <customStatusId>
claw-wrike task update --id <id> --dry-run
claw-wrike task delete --id <id>
claw-wrike task delete --id <id> --dry-run
Comments
claw-wrike comment list --task <id>
claw-wrike comment add --task <id> --text "Comment text"
claw-wrike comment update --id <id> --text "Updated text"
claw-wrike comment delete --id <id>
Contacts, Workflows, Custom Fields
claw-wrike contact list
claw-wrike contact get --id <id>
claw-wrike workflow list
claw-wrike customfield list
Utilities
claw-wrike lookup --permalink <url>
claw-wrike cache refresh
claw-wrike config show
Important Notes
- IDs: Wrike API IDs are alphanumeric strings like
IEABMHYCI5P7AYDW. They are NOT the numeric IDs in permalink URLs.
- Assignee resolution: Use names ("Jane", "Jane Doe") or IDs. Names are resolved via cached contacts.
- Custom statuses: Use
claw-wrike workflow list to find custom status IDs, then pass them to --status.
- Folders = Projects: A project is a folder with a
project property. Use folder commands for both.
- Tasks can have multiple parents: A task can belong to multiple folders/projects.
- Dry run: Use
--dry-run on create/update commands to see the API call without executing it.
- Rate limit: ~400 requests/minute. The CLI handles rate limiting and retries automatically.
Before Any Operation
- Use
claw-wrike space list or claw-wrike folder list to find the right container ID.
- Use
claw-wrike workflow list to understand available statuses before changing task status.
- Use
claw-wrike task get --id <id> to read current state before updating.
NEVER
- Never guess task or folder IDs. Always look them up first.
- Never update tasks without reading their current state.
- Never bulk-modify tasks without user confirmation.