managing-wrike

name	managing-wrike
description	Use when working with Wrike — wrike project management covering folders, projects, tasks, timelog entries, and workflow analytics. Use when auditing Wrike usage, managing tasks and projects, analyzing time tracking, or reviewing workflow health across a Wrike workspace.
connection_type	wrike
preload	false

Managing Wrike

Wrike project management analysis via the Wrike REST API.

Discovery Phase

#!/bin/bash
WRIKE_BASE="https://www.wrike.com/api/v4"

echo "=== Current User ==="
curl -s -H "Authorization: Bearer $WRIKE_TOKEN" \
  "$WRIKE_BASE/contacts?me=true" \
  | jq '.data[0] | {id, firstName, lastName, type, profiles}'

echo ""
echo "=== Account Info ==="
curl -s -H "Authorization: Bearer $WRIKE_TOKEN" \
  "$WRIKE_BASE/account" \
  | jq '.data[0] | {id, name, subscription: .subscription.type}'

echo ""
echo "=== Folders & Projects ==="
curl -s -H "Authorization: Bearer $WRIKE_TOKEN" \
  "$WRIKE_BASE/folders?project=true&fields=[\"briefDescription\"]" \
  | jq -r '.data[] | "\(.id)\t\(.title[0:30])\t\(.project.status // "folder")\t\(.scope)"' | column -t | head -25

echo ""
echo "=== Workflows ==="
curl -s -H "Authorization: Bearer $WRIKE_TOKEN" \
  "$WRIKE_BASE/workflows" \
  | jq -r '.data[] | "\(.id)\t\(.name)\tstates: \([.customStatuses[] | .name] | join(", "))"'

echo ""
echo "=== Custom Fields ==="
curl -s -H "Authorization: Bearer $WRIKE_TOKEN" \
  "$WRIKE_BASE/customfields?fields=[\"type\"]" \
  | jq -r '.data[:10][] | "\(.id)\t\(.title[0:25])\t\(.type)"' | column -t

Analysis Phase

#!/bin/bash
WRIKE_BASE="https://www.wrike.com/api/v4"
FOLDER_ID="${1:?Folder/Project ID required}"

echo "=== Tasks in Project ==="
curl -s -H "Authorization: Bearer $WRIKE_TOKEN" \
  "$WRIKE_BASE/folders/$FOLDER_ID/tasks?fields=[\"responsibleIds\",\"customStatusId\"]&pageSize=25" \
  | jq -r '.data[] | "\(.id)\t\(.title[0:40])\t\(.status)\t\(.importance)\t\(.responsibleIds | length) assignees"' | column -t

echo ""
echo "=== Task Status Distribution ==="
curl -s -H "Authorization: Bearer $WRIKE_TOKEN" \
  "$WRIKE_BASE/folders/$FOLDER_ID/tasks?fields=[\"customStatusId\"]&pageSize=100" \
  | jq '[.data[].status] | group_by(.) | map({status: .[0], count: length}) | sort_by(-.count)[]'

echo ""
echo "=== Overdue Tasks ==="
curl -s -H "Authorization: Bearer $WRIKE_TOKEN" \
  "$WRIKE_BASE/folders/$FOLDER_ID/tasks?status=Active&dueDate={\"end\":\"$(date +%Y-%m-%d)\"}&pageSize=10" \
  | jq -r '.data[]? | "\(.title[0:40])\tdue=\(.dates.due // "none")\t\(.importance)"' | column -t

echo ""
echo "=== Time Logs (last 7 days) ==="
FROM=$(date -v-7d +%Y-%m-%dT00:00:00Z 2>/dev/null || date -u -d "-7 days" +%Y-%m-%dT00:00:00Z)
curl -s -H "Authorization: Bearer $WRIKE_TOKEN" \
   \
  | jq -r  | column -t

Output Format

WRIKE PROJECT HEALTH: [project_name]
Status:         [status]
Total Tasks:    [count]
Overdue Tasks:  [count]

TASK STATUS DISTRIBUTION
Status           Count   Pct
Active           [n]     [pct]%
Completed        [n]     [pct]%
Deferred         [n]     [pct]%

TIME TRACKING (Last 7 Days)
Total Hours:     [h]
Contributors:    [count]

OVERDUE TASKS
Task                 Due Date    Priority
[title]              [date]      [importance]

Anti-Hallucination Rules

1. NEVER assume resource names — always discover via CLI/API in Phase 1 before referencing in Phase 2.
2. NEVER fabricate metric names or dimensions — verify against the service documentation or --help output.
3. NEVER mix CLI commands between service versions — confirm which version/API you are targeting.
4. ALWAYS use the discovery → verify → analyze chain — every resource referenced must have been discovered first.
5. ALWAYS handle empty results gracefully — an empty response is valid data, not an error to retry.

Counter-Rationalizations

Shortcut	Counter	Why
"I'll skip discovery and check known resources"	Always run Phase 1 discovery first	Resource names change, new resources appear — assumed names cause errors
"The user only asked for a quick check"	Follow the full discovery → analysis flow	Quick checks miss critical issues; structured analysis catches silent failures
"Default configuration is probably fine"	Audit configuration explicitly	Defaults often leave logging, security, and optimization features disabled
"Metrics aren't needed for this"	Always check relevant metrics when available	API/CLI responses show current state; metrics reveal trends and intermittent issues
"I don't have access to that"	Try the command and report the actual error	Assumed permission failures prevent useful investigation; actual errors are informative