Wrike Automation

Wrike Automation via Rube MCP

Automate Wrike project management operations through Composio's Wrike toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/wrike

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.

1. Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
2. Call RUBE_MANAGE_CONNECTIONS with toolkit wrike
3. If connection is not ACTIVE, follow the returned auth link to complete Wrike OAuth
4. 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:

1. WRIKE_GET_FOLDERS - Find the target folder/project [Prerequisite]
2. WRIKE_GET_ALL_CUSTOM_FIELDS - Get custom field IDs if needed [Optional]
3. WRIKE_CREATE_TASK - Create a new task [Required]
4. 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
• priorityBefore and priorityAfter are mutually exclusive
• Status field may not be available on Team plan
• dates.start and dates.due use 'YYYY-MM-DD' format

2. Manage Folders and Projects

When to use: User wants to create, modify, or organize folders and projects

Tool sequence:

1. WRIKE_GET_FOLDERS - List existing folders [Required]
2. WRIKE_CREATE_FOLDER - Create a new folder/project [Optional]
3. WRIKE_MODIFY_FOLDER - Update folder properties [Optional]
4. WRIKE_LIST_SUBFOLDERS_BY_FOLDER_ID - List subfolders [Optional]
5. WRIKE_DELETE_FOLDER - Delete a folder permanently [Optional]

Key parameters:

• folderId: Parent folder ID for creation; target folder ID for modification
• title: Folder name
• description: Folder description
• customItemTypeId: Set to create as a project instead of a folder
• shareds: Array of user IDs or emails to share with
• project: Filter for projects (true) or folders (false) in GET_FOLDERS

Pitfalls:

• DELETE_FOLDER is permanent and removes ALL contents (tasks, subfolders, documents)
• Cannot modify rootFolderId or recycleBinId as parents
• Folder creation auto-shares with the creator
• customItemTypeId converts a folder into a project
• GET_FOLDERS with descendants=true returns folder tree (may be large)

3. Retrieve and Track Tasks

When to use: User wants to find tasks, check status, or monitor progress

Tool sequence:

1. WRIKE_FETCH_ALL_TASKS - List tasks with optional filters [Required]
2. WRIKE_GET_TASK_BY_ID - Get detailed info for a specific task [Optional]

Key parameters:

• status: Filter by task status ('Active', 'Completed', etc.)
• dueDate: Filter by due date range (start/end/equal)
• fields: Additional response fields to include
• page_size: Results per page (1-100)
• taskId: Specific task ID for detailed retrieval
• resolve_user_names: Auto-resolve user IDs to names (default true)

Pitfalls:

• FETCH_ALL_TASKS paginates at max 100 items per page
• dueDate filter supports 'equal', 'start', and 'end' fields
• Date format: 'yyyy-MM-dd' or 'yyyy-MM-ddTHH:mm:ss'
• GET_TASK_BY_ID returns read-only detailed information
• customFields are returned by default for single task queries

4. Launch Task Blueprints

When to use: User wants to create tasks from predefined templates

Tool sequence:

1. WRIKE_LIST_TASK_BLUEPRINTS - List available blueprints [Prerequisite]
2. WRIKE_LIST_SPACE_TASK_BLUEPRINTS - List blueprints in a specific space [Alternative]
3. WRIKE_LAUNCH_TASK_BLUEPRINT_ASYNC - Launch a blueprint [Required]

Key parameters:

• task_blueprint_id: ID of the blueprint to launch
• title: Title for the root task
• parent_id: Parent folder/project ID (OR super_task_id)
• super_task_id: Parent task ID (OR parent_id)
• reschedule_date: Target date for task rescheduling
• reschedule_mode: 'RescheduleStartDate' or 'RescheduleFinishDate'
• entry_limit: Max tasks to copy (1-250)

Pitfalls:

• Either parent_id or super_task_id is required, not both
• Blueprint launch is asynchronous; tasks may take time to appear
• reschedule_date requires reschedule_mode to be set
• entry_limit caps at 250 tasks/folders per blueprint launch
• copy_descriptions defaults to false; set true to include task descriptions