| name | wrike-automation |
| description | Automate Wrike project management via Rube MCP (Composio): create tasks/folders, manage projects, assign work, and track progress. Always search tools first for current schemas. |
| type | skill |
| created | 2026-02-27T00:00:00.000Z |
| domain | productivity |
| category | automation |
| risk | critical |
| source | community |
| tags | ["skill","productivity","automation","wrike"] |
Wrike Automation via Rube MCP
Automate Wrike project management operations through Composio's Wrike toolkit via Rube MCP.
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Wrike connection via
RUBE_MANAGE_CONNECTIONS with toolkit wrike
- Always call
RUBE_SEARCH_TOOLS first to get current tool schemas
Setup
Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
- Verify Rube MCP is available by confirming
RUBE_SEARCH_TOOLS responds
- Call
RUBE_MANAGE_CONNECTIONS with toolkit wrike
- If connection is not ACTIVE, follow the returned auth link to complete Wrike OAuth
- Confirm connection status shows ACTIVE before running any workflows
Core Workflows
1. Create and Manage Tasks
When to use: User wants to create, assign, or update tasks in Wrike
Tool sequence:
WRIKE_GET_FOLDERS - Find the target folder/project [Prerequisite]
WRIKE_GET_ALL_CUSTOM_FIELDS - Get custom field IDs if needed [Optional]
WRIKE_CREATE_TASK - Create a new task [Required]
WRIKE_MODIFY_TASK - Update task properties [Optional]
Key parameters:
folderId: Parent folder ID where the task will be created
title: Task title
description: Task description (supports HTML)
responsibles: Array of user IDs to assign
status: 'Active', 'Completed', 'Deferred', 'Cancelled'
importance: 'High', 'Normal', 'Low'
customFields: Array of {id, value} objects
dates: Object with type, start, due, duration
Pitfalls:
- folderId is required; tasks must belong to a folder
- responsibles requires Wrike user IDs, not emails or names
- Custom field IDs must be obtained from GET_ALL_CUSTOM_FIELDS