# Wrike Wrike is a project management and collaboration tool offering customizable workflows, Gantt charts, reporting, and resource management to boost team productivity - **Category:** project management - **Auth:** OAUTH2 - **Composio Managed App Available?** Yes - **Tools:** 144 - **Triggers:** 0 - **Slug:** `WRIKE` - **Version:** 20260316_00 ## Tools ### Bulk modify group members **Slug:** `WRIKE_BULK_MODIFY_GROUPS` Adds or removes members for multiple Wrike groups in a single request; all specified user IDs must correspond to existing Wrike users. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `members` | array | Yes | List of group modification objects (max 20), each specifying a Wrike group and the members to add or remove. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Copy folder **Slug:** `WRIKE_COPY_FOLDER` Copies a Wrike folder synchronously to a specified parent location with customizable options. Use when duplicating folder structures, optionally copying descriptions, responsibles, custom fields, statuses, and rescheduling tasks. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `title` | string | Yes | The title for the copied folder. | | `parent` | string | Yes | The ID of the parent folder where the copy will be placed. Must be a valid Wrike folder ID. | | `folderId` | string | Yes | The ID of the folder to copy. Must be a valid Wrike folder ID. | | `entryLimit` | integer | No | Maximum number of tasks/folders/projects to copy. Use this to limit the scope of the copy operation. If not specified, all entries will be copied. | | `copyParents` | boolean | No | If true, copies the parent folder hierarchy from the original folder. Defaults to false if not specified. | | `copyStatuses` | boolean | No | If true, copies statuses from the original folder to the new folder. Defaults to false if not specified. | | `rescheduleMode` | string | No | Reschedule mode for tasks in the copied folder. Valid values: 'Start' (reschedule based on start date) or 'End' (reschedule based on end date). Only used when rescheduledDate is provided. | | `addResponsibles` | array | No | List of user IDs to add as responsibles to the copied folder. These users will be assigned to the new folder regardless of the copyResponsibles setting. | | `rescheduledDate` | string | No | Date for rescheduling tasks in the copied folder. Must be in ISO 8601 format (e.g., '2024-12-31'). Used with rescheduleMode to adjust task dates. | | `copyCustomFields` | boolean | No | If true, copies custom fields from the original folder to the new folder. Defaults to false if not specified. | | `copyDescriptions` | boolean | No | If true, copies descriptions from the original folder to the new folder. Defaults to false if not specified. | | `copyResponsibles` | boolean | No | If true, copies assignees/responsibles from the original folder to the new folder. Defaults to false if not specified. | | `copyCustomStatuses` | boolean | No | If true, copies custom statuses from the original folder to the new folder. Defaults to false if not specified. | | `removeResponsibles` | array | No | List of user IDs to remove from responsibles in the copied folder. These users will not be assigned to the new folder even if present in the original. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Copy folder async **Slug:** `WRIKE_COPY_FOLDER_ASYNC` Duplicate a folder asynchronously in Wrike, creating a copy in a specified parent location. Use when copying large folder structures that may take time to complete. Returns an async job ID for tracking progress. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `title` | string | Yes | The name assigned to the copied folder. This is a required parameter for the async copy operation. | | `parent` | string | Yes | The destination parent folder ID where the copy will be placed. Use WRIKE_GET_FOLDERS to get valid folder IDs. | | `folder_id` | string | Yes | The identifier of the folder to be copied. Must be a valid Wrike folder ID. | | `entry_limit` | integer | No | Maximum number of tasks/folders/projects to copy. This limit must be between 1 and 250, inclusive. If the folder contains more items, only the specified number will be copied. | | `copy_parents` | boolean | No | Whether to maintain folder hierarchy when copying. If true, parent-child relationships are preserved in the copy. | | `copy_statuses` | boolean | No | Whether to preserve task statuses from the original folder. If true, tasks in the copy retain their status. | | `reschedule_date` | string | No | The date for task rescheduling in ISO 8601 format (YYYY-MM-DD). If provided along with reschedule_mode, tasks will be rescheduled based on this date. | | `reschedule_mode` | string ("Start" | "End") | No | Mode for rescheduling tasks when copying a folder. | | `add_responsibles` | array | No | Additional users to assign to tasks in the new folder. Provide an array of Wrike user IDs. | | `copy_descriptions` | boolean | No | Whether to include the original folder's description in the copy. If true, descriptions are copied; otherwise, they are left empty. | | `copy_responsibles` | boolean | No | Whether to carry over original task assignments to the copied folder. If true, responsible users from original tasks are assigned to copied tasks. | | `copy_custom_fields` | boolean | No | Whether to replicate custom field data from the original folder to the copy. If true, custom field values are preserved. | | `remove_responsibles` | array | No | Users to exclude from task assignments in the copied folder. Provide an array of Wrike user IDs to remove. | | `copy_custom_statuses` | boolean | No | Whether to include custom status definitions in the copied folder. If true, custom statuses are replicated. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create account webhooks **Slug:** `WRIKE_CREATE_ACCOUNT_WEBHOOKS` Creates a webhook for the current account to receive notifications about changes. Use when you need to set up real-time event notifications for tasks, folders, or other Wrike objects. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `events` | array | No | Array of event types to listen for (e.g., TaskCreated, TaskDeleted, FolderCreated). If omitted, all events are received. | | `secret` | string | No | Client secret for event authenticity verification. Used to validate that webhook events are genuinely from Wrike. | | `hookUrl` | string | Yes | URL of the server that will receive the webhook payload. Must be a valid HTTPS URL. | | `customItemTypes` | array | No | Array of Custom Item Type IDs to limit webhooks to specific CIT changes. Only events related to these CITs will trigger the webhook. | | `parameterisedEvents` | array | No | Array of objects for filtering events with customizable fields. Each object specifies event type, custom fields, and standard fields to include. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create equipment asset **Slug:** `WRIKE_CREATE_ASSETS` Tool to create equipment/asset in Wrike. Use when you need to add new equipment or assets to track in the system. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `name` | string | Yes | The name of the equipment/asset to create. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create custom field **Slug:** `WRIKE_CREATE_CUSTOMFIELD` Tool to create a new custom field in Wrike. Use when you need to define a new custom field for tasks, folders, or projects. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `type` | string ("Text" | "DropDown" | "Numeric" | "Currency" | "Percentage" | "Date" | "Duration" | "Checkbox" | "Contacts" | "Multiple") | Yes | Type of the custom field. Determines what kind of data can be stored in this field. | | `title` | string | Yes | Title of the custom field to create | | `values` | array | No | Array of predefined option values for DropDown and Multiple type custom fields. | | `shareds` | array | No | List of user IDs to share the custom field with. Empty list means not shared with anyone. | | `spaceId` | string | No | Space ID to create the custom field in. If not specified, creates an account-level custom field. | | `contacts` | array | No | Array of contact IDs representing allowed users or invitations for Contacts type custom fields. | | `currency` | string | No | Currency code for Currency type fields (e.g., USD, EUR, GBP). Defaults to USD if not specified. | | `readOnly` | boolean | No | Whether the custom field is read-only. Defaults to false. | | `aggregation` | string ("None" | "Sum" | "Average") | No | Aggregation type for custom fields. | | `decimalPlaces` | integer | No | Number of decimal places for Numeric, Percentage, and Currency types. Defaults to 2 if not specified. | | `inheritanceType` | string ("All" | "Folders" | "Projects") | No | Inheritance type for custom fields. | | `allowOtherValues` | boolean | No | Whether users can enter custom values beyond predefined options for DropDown type. Defaults to true. | | `useThousandsSeparator` | boolean | No | Whether to use thousands separator for Numeric type fields. Defaults to false. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create a folder **Slug:** `WRIKE_CREATE_FOLDER` Creates a new Wrike subfolder within the specified `folderId`, optionally as a project if `customItemTypeId` is given; the folder is auto-shared with its creator. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `title` | string | Yes | The title for the new folder. | | `fields` | array | No | An optional list of field names to include in the response model, allowing for specific details about the created folder to be retrieved. Example fields include 'briefDescription', 'customFields', 'metadata', etc. | | `shareds` | array | No | A list of user IDs or invited user emails to share the folder with. | | `folderId` | string | Yes | The unique identifier of the parent folder where the new subfolder will be created. | | `metadata` | array | No | A list of metadata entries (key-value pairs) to associate with the newly created folder. | | `description` | string | No | An optional description for the new folder. | | `customFields` | array | No | A list of custom field entries (ID and value) to set for the new folder. | | `customColumns` | array | No | A list of custom field IDs to be associated with the folder as columns. These typically control the visibility and order of custom fields in a table view. | | `userAccessRoles` | object | No | A dictionary mapping user IDs to their access roles for this folder (e.g., 'Editor', 'Limited', 'Full', 'Owner'). The key is the user ID and the value is the access role name. | | `withInvitations` | boolean | No | A boolean flag indicating whether to include invited (pending) users in the 'ownerIds' and 'sharedIds' lists in the response. | | `customItemTypeId` | string | No | The ID of a Custom Item Type. If provided, the created folder will be a project based on this type. | | `plainTextCustomFields` | boolean | No | A boolean flag. If true, HTML tags will be stripped from custom field values. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create folder booking **Slug:** `WRIKE_CREATE_FOLDER_BOOKING` Tool to create a booking in a Wrike folder. Use when you need to allocate resources (users or placeholders) to a folder for a specific date range. Either responsibleId or responsiblePlaceholderId must be provided, and bookingDates must include at least two of: startDate, finishDate, or duration. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `folderId` | string | Yes | Unique identifier of the folder to create the booking in | | `bookingDates` | object | Yes | Object containing booking date information. Must include two of: startDate, finishDate, or duration. | | `responsibleId` | string | No | Contact ID of the user responsible for this booking. Either responsibleId or responsiblePlaceholderId must be provided. | | `effortAllocation` | object | No | Effort allocation details for the booking. | | `responsiblePlaceholderId` | string | No | Placeholder ID if booking is for a placeholder resource instead of a user. Either responsibleId or responsiblePlaceholderId must be provided. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create approval in folder **Slug:** `WRIKE_CREATE_FOLDERS_APPROVALS` Tool to create a new approval in a Wrike folder. Use when you need to create an approval workflow for folder content review. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `folderId` | string | Yes | The unique identifier of the folder where the approval will be created | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create folder comment **Slug:** `WRIKE_CREATE_FOLDERS_COMMENTS` Creates a new comment on a specified Wrike folder. Use when adding feedback, updates, or notes to a folder. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `text` | string | Yes | The comment text content. HTML format is accepted with limited tags. | | `folderId` | string | Yes | The unique identifier of the folder to add the comment to. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create timelog lock period for folder **Slug:** `WRIKE_CREATE_FOLDERS_TIMELOG_LOCK_PERIOD` Creates a timelog lock period for a specific folder. Timelogs on or before the specified period date will be locked and cannot be edited. Use when you need to prevent modifications to timelog entries up to a certain date. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `period` | string | Yes | Date in YYYY-MM-DD format specifying the timelog lock period to create. Timelogs on or before this date will be locked. | | `folderId` | string | Yes | Unique identifier of the folder for which to create a timelog lock period. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create a webhook on folder **Slug:** `WRIKE_CREATE_FOLDER_WEBHOOK` Tool to create a webhook for a Wrike folder or project. Use when you need to set up real-time notifications for events occurring within a specific folder or its subfolders. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `events` | array | No | Optional list of events to subscribe to. If not specified, all events will be received. Common events include: 'AttachmentAdded', 'AttachmentDeleted', 'TaskCreated', 'TaskDeleted', 'TaskStatusChanged', 'CommentAdded', 'CommentDeleted', etc. | | `secret` | string | No | Optional client secret to verify the authenticity of webhook events. This secret will be used to sign webhook payloads. | | `hookUrl` | string | Yes | The URL of the server that will receive the webhook payload when events occur. Must be a valid HTTPS URL. | | `folder_id` | string | Yes | The unique identifier of the folder or project to create the webhook for. Must be a valid Wrike folder ID (e.g., 'IEAGTXR7I4IHGABC'). | | `recursive` | boolean | No | Whether to listen to events for subfolders and subprojects in the hierarchy. Default is false. Set to true to track all nested elements. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create a group **Slug:** `WRIKE_CREATE_GROUP` Creates a new user group in Wrike with a specified title, optionally setting members, parent group, avatar, and custom metadata. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `title` | string | Yes | The title or name of the new group. | | `parent` | string | No | The contact ID of an existing group to set as the parent for this new group. If omitted, the group will be a top-level group. | | `members` | array | No | List of Wrike user contact IDs to add as group members. | | `metadata` | array | No | List of key-value metadata entries to associate with the group. | | `avatar__color` | string | No | The hex color code for the group's avatar background (e.g., '#FF0000' for red). | | `avatar__letters` | string | No | Up to two characters to display as the group's avatar. For example, 'MT' for 'Marketing Team'. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create invitation **Slug:** `WRIKE_CREATE_INVITATION` Invites a user to a Wrike workspace by email, optionally with name, specifying EITHER `userTypeId` OR a combination of `role`/`external`; custom email subject/message available for paid accounts. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `role` | string | No | Role for the invited user (e.g., 'Admin', 'Regular User', 'External User'). Cannot be used if `userTypeId` is specified. Can be combined with `external`. | | `email` | string | Yes | Email address of the user to invite. | | `message` | string | No | Custom message body for the invitation email (paid Wrike accounts only). | | `subject` | string | No | Custom subject for the invitation email (paid Wrike accounts only). | | `external` | boolean | No | Flags invited user as external. Cannot be used if `userTypeId` is specified. Can be combined with `role`. | | `lastName` | string | No | Last name of the invited user. | | `firstName` | string | No | First name of the invited user. | | `userTypeId` | string | No | ID of the user type to assign (e.g., Admin, Regular User, External User). Cannot be used if `role` or `external` is specified. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create space timelog lock period **Slug:** `WRIKE_CREATE_SPACES_TIMELOG_LOCK_PERIOD` Tool to create a timelog lock period for a space to prevent time entries from being edited. Use when you need to lock timelogs for specific dates, typically before creating payrolls or preparing invoices. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `period` | string | Yes | Date for the timelog lock period in YYYY-MM-DD format. This date and all prior dates will be locked for timelog editing. | | `spaceId` | string | Yes | Unique identifier of the space to create a timelog lock period for. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create space webhook **Slug:** `WRIKE_CREATE_SPACE_WEBHOOK` Tool to create a webhook on a Wrike space for receiving notifications about changes to tasks, folders, and projects. Use when you need to set up event-driven integrations for space-level changes. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `events` | array | No | List of specific event types to subscribe to. If omitted, all events are received. Examples: AttachmentAdded, AttachmentDeleted, TaskCreated, TaskTitleChanged, etc. | | `secret` | string | No | Client secret for verifying event authenticity and securing webhook payloads. | | `hookUrl` | string | Yes | URL of the server endpoint that will receive the webhook payload notifications. | | `space_id` | string | Yes | Unique identifier of the space to create the webhook for. | | `recursive` | boolean | No | If true, monitor subfolders and subprojects throughout the space hierarchy. Default is false. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create task in folder **Slug:** `WRIKE_CREATE_TASK` Creates a new task in a specified Wrike folder; if setting priority with `priorityBefore` or `priorityAfter`, the referenced task must be in the same folder or project. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `title` | string | Yes | Title of the task. | | `fields` | array | No | JSON string array specifying optional fields to include in the task details of the response. | | `follow` | boolean | No | If `True`, the creator automatically follows the task. | | `status` | string ("Active" | "Cancelled" | "Completed" | "Deferred") | No | Status of the task. Note: This feature may not be available on the Team plan. | | `parents` | array | No | List of parent folder IDs for the task. Cannot include the recycleBinId. | | `shareds` | array | No | List of user or invitation IDs to share the task with; creator is auto-shared. | | `folderId` | string | Yes | Unique identifier of the folder where the task will be created. | | `metadata` | array | No | List of key-value metadata pairs for the task. Each item requires 'key' and 'value'. | | `followers` | array | No | List of user IDs to be added as task followers. | | `importance` | string ("High" | "Low" | "Normal") | No | Importance level of the task. | | `superTasks` | array | No | List of task IDs to which this new task will be a subtask. | | `billingType` | string ("Billable" | "NonBillable" | "NonBillableAddToProjectReports") | No | Billing type for the task's timelogs. | | `description` | string | No | Detailed description of the task. | | `customFields` | array | No | List of custom fields for the task. Each item requires `id` (custom field ID) and `value`. Refer to Wrike API documentation for value formatting based on type. | | `customStatus` | string | No | Unique ID of a custom status for the task. | | `responsibles` | array | No | List of user or invitation IDs to be assigned as responsible for the task. | | `priorityAfter` | string | No | ID of an existing task to place the new task after in the list. | | `priorityBefore` | string | No | ID of an existing task to place the new task before in the list. | | `withInvitations` | boolean | No | If `True`, include invited (unregistered) users in response's `shareds` and `responsibles`. | | `customItemTypeId` | string | No | Unique ID of a Custom Item Type to use as a template for the task; task inherits its properties. | | `plainTextCustomFields` | boolean | No | If `True`, HTML tags will be stripped from custom field values before saving. | | `responsiblePlaceholders` | array | No | List of placeholder IDs (Job Roles) to be assigned as responsible for the task. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create task attachment **Slug:** `WRIKE_CREATE_TASK_ATTACHMENT` Tool to upload a file attachment to a Wrike task. Use when you need to attach files to tasks. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `file` | object | Yes | File to upload to the task. | | `taskId` | string | Yes | The ID of the task to attach the file to. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create task comment **Slug:** `WRIKE_CREATE_TASK_COMMENT` Tool to create a new comment on a Wrike task. Use when you need to add a comment or note to a task. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `text` | string | Yes | Comment text content. Supports HTML formatting with limited tags. Use HTML syntax for @mentions. | | `taskId` | string | Yes | The ID of the task to add a comment to. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create task approval **Slug:** `WRIKE_CREATE_TASKS_APPROVALS` Tool to create an approval on a specific task in Wrike. Use when you need to add an approval workflow to a task. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `taskId` | string | Yes | Unique identifier of the task to add the approval to | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create task dependency **Slug:** `WRIKE_CREATE_TASKS_DEPENDENCIES` Tool to create a new dependency relationship between Wrike tasks. Use when you need to establish that one task must be completed before another can start or finish. Both tasks must have Planned scheduling type (not Backlog) for dependencies to work. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `taskId` | string | Yes | The ID of the successor task (the task that depends on another). Must have Planned scheduling type (not Backlog). | | `relationType` | string ("FinishToStart" | "FinishToFinish" | "StartToStart" | "StartToFinish") | Yes | The type of dependency relationship between tasks | | `predecessorId` | string | Yes | The ID of the predecessor task (the task that must be completed before the successor). Must have Planned scheduling type (not Backlog). | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create task timelog **Slug:** `WRIKE_CREATE_TASKS_TIMELOGS` Tool to create a timelog entry for a specific task in Wrike. Use when you need to log time spent on a task. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `hours` | number | Yes | Number of hours tracked (decimal value, e.g., 2.5 for 2 hours and 30 minutes). | | `taskId` | string | Yes | Unique identifier of the task to log time against. | | `comment` | string | No | Optional comment describing the work performed during this time entry. | | `categoryId` | string | No | Optional timelog category ID to categorize this time entry (e.g., for billing or project tracking). | | `trackedDate` | string | Yes | Date when the time was tracked, in YYYY-MM-DD format. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create timesheet **Slug:** `WRIKE_CREATE_TIMESHEETS` Tool to create a timesheet for a user for a specified time period. Use when you need to initialize or retrieve a timesheet for a given week. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `periodStartDate` | string | Yes | The start date of the timesheet period in YYYY-MM-DD format. The API will adjust to the beginning of the week containing this date. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create workflows **Slug:** `WRIKE_CREATE_WORKFLOWS` Tool to create a new custom workflow in Wrike. Use when you need to create a new workflow with a specific name. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `name` | string | Yes | Name of the workflow to create | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete approval **Slug:** `WRIKE_DELETE_APPROVALS` Cancels/deletes an approval by its identifier. Use when removing an approval request that is no longer needed. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `approvalId` | string | Yes | The unique identifier of the approval to cancel/delete. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete asset **Slug:** `WRIKE_DELETE_ASSET` Permanently deletes a Wrike asset/equipment by assetId. Use when removing equipment that is no longer needed. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `assetId` | string | Yes | The unique identifier of the asset/equipment to be deleted. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete attachment **Slug:** `WRIKE_DELETE_ATTACHMENTS` Tool to permanently delete a Wrike attachment by its ID. Use when removing an attachment from tasks or folders. This action is irreversible. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `attachment_id` | string | Yes | The unique identifier of the attachment to delete. Must be a valid Wrike attachment ID (e.g., 'IEAGWTJBIYUICQDM'). | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete booking **Slug:** `WRIKE_DELETE_BOOKING` Permanently removes a resource booking allocation by its ID; use when deallocating resources from projects or tasks. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `bookingId` | string | Yes | The unique identifier of the booking to be removed. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete comment **Slug:** `WRIKE_DELETE_COMMENT` Permanently deletes a Wrike comment by its ID; this action is irreversible and the comment must exist. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `commentId` | string | Yes | The unique identifier of the comment to be deleted. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete custom field by id **Slug:** `WRIKE_DELETE_CUSTOM_FIELD` Permanently deletes a custom field by its ID; this action is irreversible and requires a valid, existing custom field ID. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `customFieldId` | string | Yes | The unique identifier of the custom field to be permanently deleted. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete dependencies **Slug:** `WRIKE_DELETE_DEPENDENCIES` Permanently removes a task dependency relationship by its ID; use when unlinking predecessor/successor task relationships. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `dependencyId` | string | Yes | The unique identifier of the dependency to be removed. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete folder **Slug:** `WRIKE_DELETE_FOLDER` Permanently deletes the folder specified by `folderId` and all its contents (e.g., tasks, documents, subfolders) from the Wrike workspace; this irreversible action is for when the folder is no longer needed and has no active tasks or dependencies that would block deletion. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `folderId` | string | Yes | The unique identifier of the folder to be deleted. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete timelog lock period for folder **Slug:** `WRIKE_DELETE_FOLDERS_TIMELOG_LOCK_PERIOD` Deletes a timelog lock period for a specific folder. This unlocks timelogs on or before the specified period date, allowing them to be edited again. Use when you need to remove a lock period and allow modifications to previously locked timelog entries. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `period` | string | Yes | Date in YYYY-MM-DD format specifying the timelog lock period to delete. This unlocks timelogs on or before this date. | | `folderId` | string | Yes | Unique identifier of the folder for which to delete a timelog lock period. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete group by id **Slug:** `WRIKE_DELETE_GROUP` Permanently deletes a group by its `groupId`; this action is irreversible and does not affect user accounts that were members of the group. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `groupId` | string | Yes | The unique identifier of the group to be deleted. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete invitation **Slug:** `WRIKE_DELETE_INIVTATION` Permanently deletes an existing invitation, specified by its unique `invitationId`; this action cannot be undone. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `invitationId` | string | Yes | The unique identifier of the invitation to be deleted. This ID can be obtained when an invitation is created or by listing existing invitations. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete job role **Slug:** `WRIKE_DELETE_JOB_ROLE` Permanently deletes a job role by its identifier; deleted job roles are removed from all tasks and users and cannot be restored. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `jobroleId` | string | Yes | The unique identifier of the job role to be deleted. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete space **Slug:** `WRIKE_DELETE_SPACE` Permanently deletes a Wrike space and all its contents by spaceId; this action is irreversible and should be used with caution. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `spaceId` | string | Yes | The unique identifier of the space to be deleted. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete spaces timelog lock period **Slug:** `WRIKE_DELETE_SPACES_TIMELOG` Tool to unlock (delete) a timelog lock period for a specific space in Wrike. Use when you need to remove a previously set lock period that prevents timelog modifications. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `period` | string | Yes | Date of the lock period to delete in YYYY-MM-DD format. | | `spaceId` | string | Yes | Unique identifier of the space containing the timelog lock period to delete. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete task **Slug:** `WRIKE_DELETE_TASK` Permanently deletes a Wrike task and all its associated data by its ID; this action is irreversible and the task must exist. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `taskId` | string | Yes | The unique identifier of the task to be deleted. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete timelog **Slug:** `WRIKE_DELETE_TIMELOG` Permanently deletes a Wrike timelog entry by its ID; use when removing an incorrect or obsolete time log entry. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `timelogId` | string | Yes | The unique identifier of the timelog entry to delete. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete webhook **Slug:** `WRIKE_DELETE_WEBHOOK` Tool to permanently delete a webhook by webhook_id. Use when you need to remove a webhook subscription. You can only delete webhooks created with the same API token. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `webhook_id` | string | Yes | The unique identifier of the webhook to delete. Must be a valid webhook ID created with the same API token. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Fetch all tasks **Slug:** `WRIKE_FETCH_ALL_TASKS` Fetches tasks from a Wrike account, allowing filtering by status, due date, and subfolder inclusion, with customizable response fields and pagination. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `fields` | array | No | A list of field names to include for each task in the response. Author-related fields: 'responsibleIds' (assigned users), 'sharedIds' (users task is shared with), 'authorIds' (task creators), 'followerIds' (task followers). Other common fields: 'description', 'briefDescription', 'parentIds', 'superParentIds'. Custom fields can also be requested by their ID. If omitted, a default set of fields is returned. To include metadata in the response, add 'metadata' to this list. | | `status` | string | No | Filter tasks by their status. Only tasks matching the specified status will be returned (e.g., Active, Completed). | | `dueDate` | object | No | Filter tasks by due date. Use 'equal' for an exact date match (yyyy-MM-dd), or 'start' and/or 'end' to define a date range (yyyy-MM-dd). If 'equal' is provided, 'start' and 'end' are ignored. | | `metadata` | object | No | Filter tasks by metadata key-value pairs. Provide a dict of key-value pairs, e.g. {"department": "marketing", "region": "us"}. All pairs must match (AND logic). | | `page_size` | integer | No | The number of tasks to return per page. Use with nextPageToken from the response to paginate; serialize requests across pages to avoid rate limit errors. | | `descendants` | boolean | No | If true, tasks from all subfolders and subprojects are included. If false, only tasks from the specified folder/project are returned. | | `resolve_user_names` | boolean | No | If true, automatically adds all user-related fields (authorIds, responsibleIds, sharedIds, followerIds) to the request and resolves user IDs to include user names and details directly in each task. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get account information **Slug:** `WRIKE_GET_ACCOUNT_INFORMATION` Retrieves detailed Wrike account information, where the response content is influenced by selected fields, account subscription, and user permissions. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `fields` | array | No | Optional fields to include in the response. Valid values are: 'metadata' (account metadata), 'customFields' (custom fields defined in the account), 'subscription' (subscription details including type, status, and user limit). If omitted, only default account fields are returned. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get all custom fields **Slug:** `WRIKE_GET_ALL_CUSTOM_FIELDS` Retrieves all custom field definitions (including ID, name, type, and settings) from the Wrike account; this returns the definitions themselves, not their specific values on Wrike items, and is useful for obtaining custom field IDs. #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get all webhooks **Slug:** `WRIKE_GET_ALL_WEBHOOKS` Tool to retrieve a list of all webhooks created using the same API token. Use when you need to view all webhooks configured for the authenticated API app. #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get approvals **Slug:** `WRIKE_GET_APPROVALS` Tool to retrieve all approvals accessible to the authenticated user. Use when you need to list approvals or check approval statuses across the workspace. #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get approvals by IDs **Slug:** `WRIKE_GET_APPROVALS_BY_IDS` Tool to retrieve specific Wrike approvals by their IDs (up to 100). Use when you need to fetch approval details for known approval identifiers. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `approval_ids` | array | Yes | List of approval IDs to retrieve (up to 100 IDs). Each ID should be a valid Wrike approval identifier. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get async job status **Slug:** `WRIKE_GET_ASYNC_JOB` Tool to retrieve status and details for an asynchronous job in Wrike. Use this after initiating async operations (like launch_async endpoints) to check job progress, completion status, and retrieve results. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `async_job_id` | string | Yes | The unique identifier of the asynchronous job to retrieve status for. This ID is returned when creating async operations (e.g., from launch_async endpoints). | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get attachments by IDs **Slug:** `WRIKE_GET_ATTACHMENTS` Tool to retrieve multiple Wrike attachments by their IDs (up to 100). Use when you need to fetch details for specific attachments using comma-separated attachment IDs. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `attachment_ids` | array | Yes | List of attachment IDs to retrieve (up to 100 IDs). Each ID should be a valid Wrike attachment identifier (e.g., 'IEAGWTJBIYUICQDM'). | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Download attachment **Slug:** `WRIKE_GET_ATTACHMENTS_DOWNLOAD` Tool to download a Wrike attachment file. Use when you need to retrieve the actual file content of an attachment by its ID. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `attachmentId` | string | Yes | The unique identifier of the attachment to download. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get attachment preview **Slug:** `WRIKE_GET_ATTACHMENTS_PREVIEW` Tool to download a preview version of a Wrike attachment. Use when you need to retrieve a preview image of an attachment by its ID. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `attachmentId` | string | Yes | The unique identifier of the attachment to get a preview for. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get attachment URL **Slug:** `WRIKE_GET_ATTACHMENTS_URL` Tool to get a public access URL for a Wrike attachment. Use when you need to retrieve a temporary URL to access or share an attachment. The returned URL is valid for 24 hours. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `attachmentId` | string | Yes | The unique identifier of the attachment to get the access URL for. This is a valid Wrike attachment identifier (e.g., 'IEAGWTJBIYUICQDM'). | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get bookings **Slug:** `WRIKE_GET_BOOKINGS` Retrieves one or more Wrike bookings by their IDs. Use when you need to fetch specific booking details for resource allocation and scheduling. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `bookingId` | string | Yes | One or more booking identifiers (up to 100 IDs maximum), separated by commas. Example: 'IEAGWTJBNYAAS2TV,IEAGWTJBNYAAS2T4' | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get colors **Slug:** `WRIKE_GET_COLORS` Tool to query the list of available colors in Wrike. Use when you need to retrieve color options for tasks, folders, or other Wrike entities. #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get comments **Slug:** `WRIKE_GET_COMMENTS` Tool to retrieve all comments accessible to the authorized user. Use when you need to fetch comments across tasks and folders, optionally filtered by date range or text format. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `plainText` | boolean | No | When true, returns comment text without HTML tags. When false or omitted, returns HTML-formatted text. | | `updatedDate` | string | No | Filter comments by date range in ISO 8601 format. Use format: {'start':'yyyy-MM-dd'T'HH:mm:ss'Z','end':'yyyy-MM-dd'T'HH:mm:ss'Z'}. Limited to 7 days maximum per request. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get comments by IDs **Slug:** `WRIKE_GET_COMMENTS_BY_IDS` Tool to retrieve multiple Wrike comments by their IDs. Use when you need to fetch specific comments using comma-separated comment IDs (up to 100). #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `plainText` | boolean | No | If true, returns comment text without HTML formatting tags. If false or omitted, returns HTML-formatted text. | | `comment_ids` | array | Yes | List of comment IDs to retrieve (up to 100 IDs). Each ID should be a valid Wrike comment identifier (e.g., 'IEAGWTJBIMKZ22VV'). | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get contact hourly rates **Slug:** `WRIKE_GET_CONTACT_HOURLY_RATES` Tool to retrieve hourly budget rates for up to 100 Wrike contacts. Use when you need to fetch budget rate information for one or multiple contacts. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `contactIds` | string | Yes | One or more contact IDs (comma-separated, up to 100 IDs). Example: 'KUAWZ3UC' or 'KUAWZ3UC,KX7XJIIO' | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get contacts **Slug:** `WRIKE_GET_CONTACTS` Retrieves a list of Wrike contacts (e.g., team members, clients, collaborators); response includes contact details but not their detailed task or project involvement. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `fields` | array | No | List of optional fields to include in the response. Valid values are 'customFields' (to include user custom fields) and 'metadata' (to include metadata). Standard contact properties (firstName, lastName, email, etc.) are always returned by default. | | `deleted` | boolean | No | Filter by deletion status: `true` for deleted, `false` or omitted (default) for active contacts. | | `metadata` | object | No | Filter contacts by metadata. Provide a single key-value pair to find contacts matching that exact metadata entry. Only the first key-value pair will be used if multiple are provided. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get contacts history **Slug:** `WRIKE_GET_CONTACTS_HISTORY` Tool to access field modification history for Wrike contacts. Use when you need to track changes made to contact information over time. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `contactIds` | string | Yes | Contact ID or comma-separated list of contact IDs (up to 100) to retrieve history for. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get contact timelogs **Slug:** `WRIKE_GET_CONTACT_TIMELOGS` Tool to retrieve all timelog records created by a specific contact in Wrike. Use when you need to query time tracking entries for a particular user. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `me` | boolean | No | If true, only timelog records of the requesting user are returned. | | `subTasks` | boolean | No | If true, adds subtasks to search scope. | | `contactId` | string | Yes | The unique identifier of the contact to retrieve timelogs for. | | `plainText` | boolean | No | If true, get comment text as plain text, HTML otherwise. | | `createdDate` | string | No | Created date filter, date match or range. Format: yyyy-MM-dd'T'HH:mm:ss'Z' (time is optional). Use JSON format for ranges: {"start": "2023-01-01", "end": "2023-12-31"} | | `descendants` | boolean | No | If true, adds all descendant tasks to search scope. | | `trackedDate` | string | No | Tracked date filter, date match or range. Format: yyyy-MM-dd'T'HH:mm:ss'Z' (time is optional). Use JSON format for ranges: {"start": "2023-01-01", "end": "2023-12-31"} or exact match: {"equal": "2023-06-15"} | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get custom item types **Slug:** `WRIKE_GET_CUSTOM_ITEM_TYPES` Tool to retrieve all custom item types from Wrike. Use when you need to discover available custom item type definitions for creating work items or understanding the custom item type structure. #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get dependencies by IDs **Slug:** `WRIKE_GET_DEPENDENCIES` Tool to retrieve one or more Wrike dependencies by their IDs (up to 100). Use when you need to fetch details for specific dependencies using comma-separated dependency IDs. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `dependency_ids` | array | Yes | List of dependency IDs to retrieve. Each ID should be a valid Wrike dependency identifier (e.g., 'MgAAAAECjuFSMwAAAAECjuGr'). Up to 100 IDs can be provided. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get folder bookings **Slug:** `WRIKE_GET_FOLDER_BOOKINGS` Tool to query bookings for a specific folder in Wrike. Use when you need to retrieve booking information for resource allocation within a particular folder or project. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `folderId` | string | Yes | Unique identifier of the folder to query bookings from. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get folders **Slug:** `WRIKE_GET_FOLDERS` Retrieves folders and/or projects from Wrike, with filters; when using `nextPageToken`, all other filter parameters must match the initial request. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `fields` | string | No | JSON array string of optional fields to include in the response for each folder. Only works when query returns 'folders' kind (not 'folderTree'). Valid field values: 'attachmentCount', 'briefDescription', 'customColumnIds', 'customFields', 'hasAttachments', 'metadata', 'space'. Note: 'sharedIds' is NOT a valid field value - it's already included in the default response. Example: '["customFields", "metadata"]' | | `deleted` | boolean | No | True to retrieve folders from the Recycle Bin; false or omitted to retrieve from Root. | | `project` | boolean | No | Filter by entity type: true for projects, false for folders. If omitted, both are returned. | | `metadata` | object | No | Filter folders based on their metadata. Provide a dictionary object (not a JSON string) of metadata field names and their expected values. | | `pageSize` | integer | No | Maximum number of folders per page (1-1000). Only "folders" kind is supported for pagination. Not supported when descendants=true (which returns "folderTree" kind). Cannot be used together with descendants=true or nextPageToken with descendants=true. | | `permalink` | string | No | Folder permalink for an exact match. | | `descendants` | boolean | No | Include all descendant folders in the search scope; false to search only within the specified folder(s). | | `updatedDate` | object | No | Filter folders by their last updated date. Provide a dictionary object (not a JSON string) with 'start', 'end', or 'equal' keys. Date format: yyyy-MM-dd'T'HH:mm:ss'Z' or yyyy-MM-dd'T'HH:mm:ssXXX. | | `customFields` | array | No | Filter folders by custom field values. Provide a list of filters, each specifying the custom field ID and value, or ID, comparator, and value. Example: `[{"id": "IEAGAAAAKZ7A____", "value": "Value"}]`. | | `contractTypes` | array | No | Filter folders by a list of contract type IDs. | | `nextPageToken` | string | No | Pagination token from a previous response to retrieve the next page. All other filter parameters must match the initial request. Only supported when kind="folders" (not supported for "folderTree"). Not supported when descendants=true (which returns "folderTree" kind). | | `customItemTypes` | array | No | Filter by a list of custom item type IDs. Standard types like 'project' or 'folder' IDs are not allowed. | | `withInvitations` | boolean | No | Include invitations in the 'sharedIds' list of the response. | | `plainTextCustomFields` | boolean | No | True to strip HTML tags from custom field values in the response. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get folder approvals **Slug:** `WRIKE_GET_FOLDERS_APPROVALS` Tool to retrieve all approvals from a specific Wrike folder. Use when you need to fetch approval details for a folder using its folder ID. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `folder_id` | string | Yes | The unique identifier of the folder to retrieve approvals from. Should be a valid Wrike folder ID (e.g., 'IEAAAAAAKUAAAAAA'). | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get folder attachments **Slug:** `WRIKE_GET_FOLDERS_ATTACHMENTS` Tool to retrieve all attachments from a specific Wrike folder. Use when you need to fetch attachment metadata and optionally download URLs for files in a folder. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `folderId` | string | Yes | The ID of the folder to retrieve attachments from. This is the Wrike folder identifier (e.g., 'IEAAAAAAKUAAAAAA'). | | `withUrls` | boolean | No | Optional parameter to include download URLs for attachments. When set to true, the response includes 'url' field with links valid for 24 hours. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get folders by IDs **Slug:** `WRIKE_GET_FOLDERS_BY_IDS` Tool to retrieve multiple Wrike folders by their IDs. Use when you need to fetch details for specific folders using comma-separated folder IDs. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `folder_ids` | array | Yes | List of folder IDs to retrieve. Each ID should be a valid Wrike folder identifier (e.g., 'IEAAAAAAKUAAAAAA'). The endpoint returns comprehensive folder details including metadata and customFields by default. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get folder comments **Slug:** `WRIKE_GET_FOLDERS_COMMENTS` Tool to retrieve comments from a specific Wrike folder. Use when you need to fetch all comments associated with a folder. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `folderId` | string | Yes | The ID of the folder to retrieve comments from. This should be a valid Wrike folder identifier (e.g., 'IEAAAAAAKUAAAAAA'). | | `plainText` | boolean | No | If true, returns comments without HTML formatting tags. Default is false. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get folders history **Slug:** `WRIKE_GET_FOLDERS_HISTORY` Tool to access field modification history for Wrike folders. Use when you need to track changes made to folder information over time. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `folderIds` | string | Yes | Folder ID or comma-separated list of folder IDs (up to 100) to retrieve history for. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get folder hourly rates **Slug:** `WRIKE_GET_FOLDERS_HOURLY` Tool to retrieve hourly budget rates for a specific Wrike folder. Use when you need to fetch budget rate information configured for a folder or project. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `folderId` | string | Yes | The unique identifier of the folder to retrieve hourly budget rates for. This is an alphanumeric string (e.g., 'IEAG2Y72I4LAAAAA'). | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get folder rollups **Slug:** `WRIKE_GET_FOLDERS_ROLLUPS` Tool to query rollup settings for items in a folder. Use when you need to fetch rollup configuration for a specific folder. Pagination is supported for folders with descendants=true, applying to the entire folder hierarchy. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `folderId` | string | Yes | The unique identifier for the folder whose rollup settings to retrieve. This is an alphanumeric string (e.g., 'IEAABBBBI4LAAAAA'). | | `pageSize` | integer | No | The number of rollup items to return per page. Default is 1000, maximum is 1000. | | `descendants` | boolean | No | Include descendants in rollup query. When true, pagination applies to the entire folder hierarchy. Default page size is 1000, maximum is 1000 items per page. | | `nextPageToken` | string | No | Token to retrieve the next page of results. Obtained from the previous response when pagination is active. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get folder tasks **Slug:** `WRIKE_GET_FOLDERS_TASKS` Query tasks within a specific folder. Use this to retrieve all tasks contained in a folder, with optional filtering by status, due date, and metadata. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `fields` | array | No | A list of field names to include for each task in the response. Common fields: 'description', 'briefDescription', 'parentIds', 'superParentIds', 'responsibleIds' (assigned users), 'sharedIds' (users task is shared with), 'authorIds' (task creators), 'followerIds' (task followers). Custom fields can also be requested by their ID. If omitted, a default set of fields is returned. | | `status` | string | No | Filter tasks by their status. Only tasks matching the specified status will be returned (e.g., Active, Completed). | | `dueDate` | object | No | Filter tasks by due date. Use 'equal' for an exact date match (yyyy-MM-dd), or 'start' and/or 'end' to define a date range (yyyy-MM-dd). If 'equal' is provided, 'start' and 'end' are ignored. | | `folderId` | string | Yes | The Wrike folder ID to query tasks from. This is an opaque text string (e.g., 'IEAGTXRI') from which to retrieve tasks. Max 256 characters. | | `metadata` | object | No | Filter tasks by metadata key-value pairs. Provide a dict of key-value pairs, e.g. {"department": "marketing", "region": "us"}. All pairs must match (AND logic). | | `page_size` | integer | No | The number of tasks to return per page. | | `descendants` | boolean | No | If true, tasks from all subfolders are included. If false, only tasks from the specified folder are returned. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get folder timelog lock periods **Slug:** `WRIKE_GET_FOLDERS_TIMELOG_LOCK_PERIODS` Tool to query timelog lock periods for a specific folder. Use when you need to check which time periods are locked for timelog entries in a folder. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `folderId` | string | Yes | The unique identifier of the folder to query timelog lock periods for. This is an alphanumeric string representing a Wrike folder ID. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get folders timelogs **Slug:** `WRIKE_GET_FOLDERS_TIMELOGS` Tool to retrieve all timelog records for a specific folder. Use when you need to query time tracking data for a folder and its tasks. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `me` | boolean | No | If true, only timelog records of the requesting user are returned | | `folderId` | string | Yes | The folder ID to retrieve timelogs for | | `subTasks` | boolean | No | If true, adds subtasks to search scope. Defaults to true | | `plainText` | boolean | No | If true, get comment text as plain text, HTML otherwise. Defaults to false | | `createdDate` | string | No | Created date filter, date match or range. Format: yyyy-MM-dd'T'HH:mm:ss'Z' ('T'HH:mm:ss is optional). Use 'start' and/or 'end' keys for range filtering as JSON string, e.g., '{"start":"2023-01-01","end":"2023-12-31"}' | | `descendants` | boolean | No | If true, adds all descendant tasks to search scope. Defaults to true | | `trackedDate` | string | No | Tracked date filter, date match or range. Format: yyyy-MM-dd'T'HH:mm:ss'Z' ('T'HH:mm:ss is optional). Use 'start', 'end', or 'equal' keys for filtering as JSON string, e.g., '{"equal":"2023-06-15"}' or '{"start":"2023-01-01","end":"2023-12-31"}' | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Convert legacy v2 IDs to v4 **Slug:** `WRIKE_GET_IDS` Tool to convert legacy Wrike API v2 IDs to current v4 format. Use when you need to work with numeric IDs from the Wrike interface or legacy integrations and convert them to the alphanumeric v4 IDs required by the current API. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `ids` | array | Yes | Array of legacy API v2 IDs to convert to v4 format. These are typically numeric IDs as shown in the Wrike interface. | | `type` | string | Yes | Type of legacy ID being converted. Valid values include: ApiV2Task, ApiV2Folder, ApiV2User, ApiV2Contact, ApiV2Comment, ApiV2Attachment, ApiV2Timelog. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get specific contact information **Slug:** `WRIKE_GET_INFORMATION_ABOUT_SPECIFIC_CONTACT` Retrieves detailed information for a specific Wrike contact using their unique `contactId`, optionally including `metadata` and `customFields` if specified in the `fields` parameter. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `fields` | array | No | Optional list of specific fields (e.g., `metadata`, `customFields`) to include; returns default fields if omitted. | | `contactId` | string | Yes | The unique identifier of the contact to retrieve information for. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get job roles by IDs **Slug:** `WRIKE_GET_JOB_ROLES` Tool to retrieve details for one or more Wrike job roles by job role IDs. Use when you need to fetch information about specific job roles. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `jobrole_ids` | string | Yes | One or more job role identifiers, comma-separated (e.g., 'IEAGWTJBM4AATOMS,IEAGWTJBM4AATOMU'). Maximum 100 IDs per request. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get placeholder hourly rates **Slug:** `WRIKE_GET_PLACEHOLDER_HOURLY_RATES` Tool to retrieve hourly budget rates for one or more Wrike placeholders. Use when you need to fetch budget rate information for placeholders, supporting up to 100 IDs in a single request. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `placeholderIds` | string | Yes | Comma-separated list of placeholder IDs to retrieve hourly rates for (up to 100). Example: 'IEAGWTJBNMAATZP5,IEAGWTJBNMAATZQA'. Each ID is an alphanumeric string representing a unique placeholder. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get placeholders by IDs **Slug:** `WRIKE_GET_PLACEHOLDERS` Tool to retrieve details for one or more Wrike placeholders by their IDs. Use when you need to fetch information about specific placeholders, supporting up to 100 IDs in a single request. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `placeholderIds` | string | Yes | Comma-separated list of placeholder IDs to retrieve (up to 100). Example: 'IEAGWTJBNMAATZP5,IEAGWTJBNMAATZQA'. Each ID is an alphanumeric string representing a unique placeholder. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get space by ID **Slug:** `WRIKE_GET_SPACE` Tool to retrieve details for a single Wrike space by spaceId. Use when you need to fetch complete information about a specific space, typically after listing spaces to select one. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `fields` | array | No | A list of optional field names to include in the response. Common fields include: 'accessType', 'archived', 'members', 'guestRoleId', etc. If omitted, a default set of fields will be returned. | | `spaceId` | string | Yes | The unique identifier of the Wrike space to retrieve. This is an alphanumeric string (e.g., 'IEAG2Y72I4LAAAAA'). | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get space custom item types **Slug:** `WRIKE_GET_SPACE_CUSTOM_ITEM_TYPES` Tool to retrieve all custom item types scoped to a specific Wrike space. Use when you need to discover available custom item types for a space before creating work items based on these types. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `spaceId` | string | Yes | The unique identifier of the Wrike space to retrieve custom item types for. This is an alphanumeric string (e.g., 'MQAAAAECjxZu'). | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get space folders **Slug:** `WRIKE_GET_SPACE_FOLDERS` Tool to retrieve the folder tree for a specific Wrike space. Use when you need to list all folders and projects within a space, optionally filtered by project type, authors, owners, title, or custom statuses. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `title` | string | No | Filter folders by title. Returns folders whose title contains the specified string (case-insensitive). | | `fields` | array | No | Optional fields to include in response. Valid values: 'attachmentCount', 'briefDescription', 'customColumnIds', 'customFields', 'hasAttachments', 'metadata', 'space'. | | `owners` | array | No | Filter folders by owner IDs. Only returns folders owned by the specified user IDs. | | `authors` | array | No | Filter folders by author IDs. Only returns folders created by the specified user IDs. | | `project` | boolean | No | Filter by project type - true for projects only, false for folders only. If omitted, returns both folders and projects. | | `spaceId` | string | Yes | The unique identifier of the Wrike space to retrieve folders from. This is an alphanumeric string (e.g., 'IEAG2Y72I4LAAAAA'). | | `customStatuses` | array | No | Filter folders by custom workflow status IDs. Only returns folders with the specified custom status IDs. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get space custom fields **Slug:** `WRIKE_GET_SPACES_CUSTOMFIELDS` Tool to retrieve all custom fields defined for a specific Wrike space. Use when you need to discover what custom fields are available in a space before querying tasks or folders with custom field data. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `spaceId` | string | Yes | The unique identifier of the space for which to query custom fields. This is an alphanumeric string (e.g., 'IEAG2Y72I4LAAAAA'). | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get spaces tasks **Slug:** `WRIKE_GET_SPACES_TASKS` Tool to query tasks within a specific Wrike space. Use when you need to retrieve tasks from a particular space, with optional filtering by status, importance, title, and other criteria. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `title` | string | No | Title filter for exact match. Only tasks with this exact title will be returned. | | `fields` | array | No | Array of optional fields to include in the response. Valid fields: authorIds, hasAttachments, attachmentCount, parentIds, superParentIds, sharedIds, responsibleIds, description, briefDescription, recurrent, superTaskIds, subTaskIds, dependencyIds, customFields, metadata. | | `status` | string ("Active" | "Completed" | "Deferred" | "Cancelled") | No | Task status values. | | `spaceId` | string | Yes | The ID of the space to query tasks from. Use the ListSpaces action to discover valid spaceIds. | | `subTasks` | boolean | No | Include subtasks in the response. If true, subtasks will be included alongside parent tasks. | | `sortField` | string | No | Field to sort the results by. Common values: CreatedDate, UpdatedDate, CompletedDate, DueDate, Title, Status, Importance. | | `sortOrder` | string ("Asc" | "Desc") | No | Sort order values. | | `importance` | string ("High" | "Normal" | "Low") | No | Task importance values. | | `descendants` | boolean | No | Query tasks in that folder and its subfolders. If true, tasks from all subfolders are included. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get space workflows **Slug:** `WRIKE_GET_SPACES_WORKFLOWS` Tool to query workflows for a specific Wrike space. Use when you need to retrieve the list of available workflows and their custom statuses for a space. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `spaceId` | string | Yes | The unique identifier of the space to query workflows for. This is an alphanumeric string (e.g., 'IEAG2Y72I4LAAAAA'). Use the List Spaces action to discover valid spaceIds. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get space timelog lock periods **Slug:** `WRIKE_GET_SPACE_TIMELOG_LOCK_PERIODS` Tool to query timelog lock periods for a specific space. Use when you need to check which time periods are locked for timelog entries in a space. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `spaceId` | string | Yes | The unique identifier of the space to query timelog lock periods for. This is an alphanumeric string representing a Wrike space ID. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get specific user **Slug:** `WRIKE_GET_SPECIFIC_USER` Retrieves detailed information about a specific user in Wrike using their unique user ID. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `userId` | string | Yes | The unique Wrike user ID (8-character alphanumeric string, e.g., 'KUAWZ3UC'). Note: 'me' is NOT supported as a value. To get the current user's ID, first call the GET /contacts endpoint and look for the contact with 'me': true in the response. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get task by id **Slug:** `WRIKE_GET_TASK_BY_ID` Retrieves read-only detailed information for a specific Wrike task by its unique ID, optionally allowing specification of fields to include in the response. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `fields` | string | No | A JSON array string of optional fields to include in the response (e.g., '["attachmentCount"]'). Valid fields include: attachmentCount, effortAllocation, billingType, etc. Note: customFields are returned by default for single task queries and should NOT be specified in this parameter. If not provided, a default set of fields (including customFields) will be returned. | | `taskId` | string | Yes | The Wrike API task ID to retrieve. This is an opaque text string (e.g., 'IEAGTXRUKQPN7777') - do not rely on format patterns. Max 256 characters. Note: Phone numbers, numeric-only strings, or other non-Wrike task ID formats are not valid. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get task dependencies **Slug:** `WRIKE_GET_TASK_DEPENDENCIES` Retrieves all dependency relationships for a specific task. Use when you need to see which tasks the specified task depends on (predecessors) or which tasks depend on it (successors). #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `taskId` | string | Yes | The unique identifier of the task to retrieve dependencies for. This is a Wrike task ID (e.g., 'IEAGTXRUKQPN7777'). | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get task approvals **Slug:** `WRIKE_GET_TASKS_APPROVALS` Retrieves all approval records for a specific task. Use when you need to see approval workflow status and decisions for a task. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `taskId` | string | Yes | The unique identifier of the task to retrieve approvals for. This is a Wrike task ID (e.g., 'IEAGTXRUKQPN7777'). | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get task attachments **Slug:** `WRIKE_GET_TASKS_ATTACHMENTS` Tool to retrieve all attachments from a specific Wrike task. Use when you need to fetch attachment metadata and optionally download URLs for files attached to a task. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `taskId` | string | Yes | The unique identifier for the task from which to retrieve attachments. This is a Wrike task ID (e.g., 'IEAGTXRUKQPN7777'). | | `withUrls` | boolean | No | Optional parameter to include download URLs for attachments. When set to true, the response includes 'url' field with links valid for 24 hours. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get task comments **Slug:** `WRIKE_GET_TASKS_COMMENTS` Tool to retrieve all comments from a specific Wrike task. Use when you need to fetch comments associated with a task. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `taskId` | string | Yes | The unique identifier of the task to retrieve comments from. This is a Wrike task ID (e.g., 'IEAGTXRUKQPN7777'). | | `plainText` | boolean | No | If true, returns comment text as plain text without HTML formatting. If false or omitted, returns HTML-formatted text. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get tasks history **Slug:** `WRIKE_GET_TASKS_HISTORY` Query task field modification history for up to 100 tasks. Use when you need to retrieve the history of changes made to task fields. Returns information about who changed what fields, when the changes occurred, and the old and new values. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `taskIds` | string | Yes | Comma-separated list of task IDs to query history for (up to 100 task IDs). Each task ID is an alphanumeric string (e.g., 'MAAAAAECjuNy,IEAG2Y72I4LAAAAA'). | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get task rollups **Slug:** `WRIKE_GET_TASKS_ROLLUPS` Tool to query rollup settings for a specific task. Use when you need to retrieve the rollup configuration that determines how custom field values are aggregated from subtasks. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `taskId` | string | Yes | The unique identifier of the task whose rollup settings you want to retrieve. This is an alphanumeric string (e.g., 'MAAAAAECjzae'). | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get task timelog lock periods **Slug:** `WRIKE_GET_TASKS_TIMELOG_LOCK_PERIODS` Tool to query timelog lock periods for a specific task. Use when you need to check which time periods are locked for timelog entries on a task. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `taskId` | string | Yes | The unique identifier of the task to query timelog lock periods for. This is an alphanumeric string representing a Wrike task ID. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get task timelogs **Slug:** `WRIKE_GET_TASK_TIMELOGS` Retrieves all timelog records for a specific task. Use when you need to see time tracking entries for a task. Supports filtering by creation date, tracked date, and user. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `me` | boolean | No | If true, only returns timelogs created by the requesting user. If false or omitted, returns all timelogs for the task. | | `taskId` | string | Yes | The unique identifier of the task to retrieve timelogs for. This is a Wrike task ID (e.g., 'IEAGTXRUKQPN7777'). | | `subTasks` | boolean | No | If true, includes timelogs from subtasks in the search. If false, only includes timelogs from the specified task. | | `plainText` | boolean | No | If true, returns comment text as plain text. If false, returns comments in HTML format. | | `createdDate` | string | No | Filter by creation date. Format: yyyy-MM-dd'T'HH:mm:ss'Z' (time part is optional). Can be exact match or range using start/end. Example for range: '{"start":"2023-01-01","end":"2023-12-31"}'. Example for exact: '{"equal":"2023-06-15"}'. | | `descendants` | boolean | No | If true, includes timelogs from all descendant tasks in the search. If false, only includes timelogs from the specified task. | | `trackedDate` | string | No | Filter by tracked date (the date the work was performed). Format: yyyy-MM-dd'T'HH:mm:ss'Z' (time part is optional). Can be exact match or range using start/end/equal. Example: '{"start":"2023-01-01","end":"2023-12-31"}' or '{"equal":"2023-06-15"}'. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get timelog categories **Slug:** `WRIKE_GET_TIMELOG_CATEGORIES` Tool to query the list of timelog categories in Wrike. Use when you need to retrieve available time tracking categories for categorizing timelog entries. #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get timelogs **Slug:** `WRIKE_GET_TIMELOGS` Retrieves timelog records from Wrike with optional filters for dates, users, and task scope. Use to query time tracking data across tasks and projects. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `me` | boolean | No | If true, only timelog records of the requesting user are returned. | | `subTasks` | boolean | No | If true, adds subtasks to search scope; if false, only parent tasks are included. | | `plainText` | boolean | No | If true, comment text is returned as plain text; if false (default), HTML format is used. | | `createdDate` | string | No | Created date filter, date match or range. Format: yyyy-MM-dd'T'HH:mm:ss'Z' ('T'HH:mm:ss is optional). Example: '{"start":"2023-01-01","end":"2023-12-31"}' for range, or '{"equal":"2023-06-15"}' for exact match. | | `descendants` | boolean | No | If true, adds all descendant tasks to search scope; if false, only direct tasks are included. | | `trackedDate` | string | No | Tracked date filter, date match or range. Format: yyyy-MM-dd'T'HH:mm:ss'Z' ('T'HH:mm:ss is optional). Example: '{"start":"2023-01-01","end":"2023-12-31"}' for range, or '{"equal":"2023-06-15"}' for exact match. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get timelogs by IDs **Slug:** `WRIKE_GET_TIMELOGS_BY_IDS` Retrieves detailed information for one or more Wrike timelogs by their unique IDs (up to 100), optionally including export and lock status. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `fields` | string | No | Optional fields to include in the response. Valid values: 'exportStatus' (export status of the timelog), 'lockStatus' (lock status of the timelog). Provide as a JSON array string. Example: '["exportStatus","lockStatus"]' | | `timelogId` | string | Yes | Comma-separated list of timelog IDs to retrieve (up to 100 IDs). Example: 'IEAGWTJBJQAGDWZX,IEAGWTJBJQAGDWZY' | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get timesheets **Slug:** `WRIKE_GET_TIMESHEETS` Tool to query timesheets from Wrike. Use when you need to retrieve user timesheets showing weekly tracked time, approval status, and timesheet periods. #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get timesheet submission rules **Slug:** `WRIKE_GET_TIMESHEET_SUBMISSION_RULES` Tool to retrieve global timesheet submission rules across all work schedules. Use when you need to check timesheet submission configurations globally. #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get API version **Slug:** `WRIKE_GET_VERSION` Tool to retrieve current Wrike API version information. Use when you need to check the API version being used or verify API compatibility. #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get webhook by ID **Slug:** `WRIKE_GET_WEBHOOK_BY_ID` Tool to retrieve details for a specific webhook by webhook_id. Use when you need to inspect webhook configuration including the hook URL, status, events, and scope. You can only access webhooks created with the same API token. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `webhook_id` | string | Yes | The unique identifier of the webhook to retrieve. Must be a valid webhook ID created with the same API token. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get work schedule timesheet rules **Slug:** `WRIKE_GET_WORKSCHEDULES_TIMESHEET` Tool to retrieve timesheet submission rules for a specific work schedule. Use when you need to check the configuration of timesheet submission requirements for a work schedule. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `workschedule_id` | string | Yes | The ID of the work schedule to retrieve timesheet submission rules for. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Launch folder blueprint async **Slug:** `WRIKE_LAUNCH_FOLDER_BLUEPRINT_ASYNC` Asynchronously launches a new project or folder structure in Wrike from a specified Folder Blueprint. Important Notes: - The folder_blueprint_id must be an actual launchable blueprint, NOT a BpRoot container. - Use WRIKE_LIST_FOLDER_BLUEPRINTS to get blueprint IDs. Look for child blueprints within the tree structure. - Blueprints with scope 'BpRoot' are root containers and cannot be launched directly. - The blueprint must fit within 250 items (subfolders, subprojects, and subtasks count towards this limit). - Returns an async job ID that can be used to track progress via the Async Job endpoint. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `title` | string | Yes | The title for the new root folder created from the blueprint. | | `parent` | string | Yes | The unique identifier of the parent folder where the blueprint structure will be created. Use WRIKE_GET_FOLDERS to get valid folder IDs. | | `entry_limit` | integer | No | The maximum number of tasks and folders that can be created from the blueprint. This limit must be between 1 and 250, inclusive. If the blueprint contains more items, the operation may fail or be partially completed. | | `title_prefix` | string | No | A prefix to be added to the titles of all tasks and folders copied from the blueprint. If not provided, original titles are used. | | `reschedule_date` | string | No | The new start date for all rescheduled tasks in the format YYYY-MM-DD. If provided, tasks will be rescheduled based on this date and the reschedule_mode. | | `reschedule_mode` | string | No | Defines how tasks are rescheduled. Common modes might include shifting tasks relative to the reschedule_date or anchoring them. Consult Wrike API documentation for specific values. Examples: 'Preserve', 'Shift'. | | `copy_attachments` | boolean | No | If true, attachments from the blueprint will be copied. Defaults to true if not specified. | | `copy_descriptions` | boolean | No | Specifies whether to copy descriptions from the blueprint's tasks and folders. If true, descriptions are copied; otherwise, they are left empty. Defaults to true if not specified. | | `copy_responsibles` | boolean | No | If true, responsible assignments from the blueprint will be copied to the new tasks. Defaults to true if not specified. | | `copy_custom_fields` | boolean | No | If true, custom field values from the blueprint will be copied to the new tasks and folders. Defaults to true if not specified. | | `folder_blueprint_id` | string | Yes | The unique identifier of the folder blueprint to be launched. Must be an actual blueprint ID (not a BpRoot container). Use WRIKE_LIST_FOLDER_BLUEPRINTS to get valid blueprint IDs - look for blueprints that are NOT 'BpRoot' scope. | | `notify_responsibles` | boolean | No | If true, users assigned as responsibles for tasks in the blueprint will be notified. Defaults to true if not specified. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Launch Task Blueprint Async **Slug:** `WRIKE_LAUNCH_TASK_BLUEPRINT_ASYNC` Asynchronously launches a Wrike Task Blueprint to create tasks/projects, requiring either `super_task_id` (parent task) or `parent_id` (parent folder/project) for placement. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `title` | string | Yes | Title for the root task created from the blueprint. | | `parent_id` | string | No | ID of an existing parent folder/project for the new task(s); either this or `super_task_id` is required. | | `entry_limit` | integer | No | Maximum number of tasks/folders to copy from blueprint (1-250). | | `title_prefix` | string | No | Prefix for titles of all tasks created from this blueprint. | | `super_task_id` | string | No | ID of an existing parent task for the new task(s); either this or `parent_id` is required. | | `reschedule_date` | string | No | Target date (yyyy-MM-dd) for rescheduling tasks; requires `reschedule_mode`. | | `reschedule_mode` | string | No | How tasks are rescheduled if `reschedule_date` is set; valid values: `RescheduleStartDate`, `RescheduleFinishDate`. | | `copy_attachments` | boolean | No | Copy attachments from blueprint tasks to new tasks. | | `copy_descriptions` | boolean | No | Copy blueprint task descriptions to new tasks; if false or omitted, new tasks will have empty descriptions. | | `copy_responsibles` | boolean | No | Assign users responsible for blueprint tasks to the newly created tasks. | | `task_blueprint_id` | string | Yes | Unique identifier of the task blueprint to launch. | | `copy_custom_fields` | boolean | No | Copy custom field values from blueprint tasks to new tasks. | | `notify_responsibles` | boolean | No | Notify users responsible for blueprint tasks when new tasks are created. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List all attachments **Slug:** `WRIKE_LIST_ATTACHMENTS` Tool to retrieve all attachments from the Wrike account. Use when you need to list attachments with optional date filtering and download URLs. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `versions` | boolean | No | When set to true, includes version information for attachments in the response. | | `withUrls` | boolean | No | When set to true, includes download URLs for attachments in the response. URLs are valid for 24 hours from the time of the request. | | `createdDate` | object | No | Date range filter for attachments. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List Folder Blueprints **Slug:** `WRIKE_LIST_FOLDER_BLUEPRINTS` Retrieves all account-level Folder Blueprints, which are templates for standardizing folder/project creation with predefined structures, custom fields, and workflows. #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List all placeholders **Slug:** `WRIKE_LIST_PLACEHOLDERS` Retrieves all placeholders accessible to the authenticated user; placeholders are templates used in Wrike for creating standardized tasks or projects. #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List space folder blueprints **Slug:** `WRIKE_LIST_SPACE_FOLDER_BLUEPRINTS` Lists all folder blueprints (templates for new folders/projects) within a specified Wrike space, requiring a valid and accessible space ID. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `space_id` | string | Yes | The unique identifier of the Wrike space from which to list folder blueprints. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List spaces **Slug:** `WRIKE_LIST_SPACES` Tool to list spaces the authorized user can access. Use when you need to discover valid spaceIds for downstream space-scoped operations like listing space blueprints. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `withInvitations` | boolean | No | Include pending invitations in the 'sharedIds' list of the response. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List space task blueprints **Slug:** `WRIKE_LIST_SPACE_TASK_BLUEPRINTS` Lists task blueprints (templates for creating tasks with consistent structures) available in a specific, accessible Wrike space. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `limit` | integer | No | Maximum total number of task blueprints to return. | | `space_id` | string | Yes | Unique identifier of the Wrike space from which to list task blueprints. | | `page_size` | integer | No | Number of task blueprints to return per page for pagination. | | `next_page_token` | string | No | Token from the previous page's response to retrieve the next page of results; if empty or omitted, fetches the first page. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List subfolders by folder id **Slug:** `WRIKE_LIST_SUBFOLDERS_BY_FOLDER_ID` Lists subfolders (metadata only, not their contents) for an existing Wrike folder specified by `folderId`, supporting recursive descent, filtering, and pagination. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `fields` | array | No | Optional fields to include in the response for each folder (e.g., 'metadata', 'customFields'). | | `project` | boolean | No | Set true for projects only, false for regular folders only; omit for both or API default. | | `folderId` | string | Yes | ID of the parent folder. | | `metadata` | object | No | Filters folders by metadata using a dictionary of key-value pairs for exact match. | | `pageSize` | integer | No | Maximum folders per page (API default e.g., 100, max 1000). | | `permalink` | string | No | Permalink for an exact match search of the folder to fetch subfolders from. | | `descendants` | boolean | No | Set to true to include all descendant subfolders; false for direct children only. | | `updatedDate` | object | No | Filters folders by last updated date using comparators (e.g., 'LessThan', 'EqualTo') or a date range ('start', 'end' keys). Dates: 'yyyy-MM-dd' or 'yyyy-MM-ddTHH:mm:ssZ'. | | `customFields` | array | No | Filters folders by custom field values using a list of filter objects (e.g., `{'id': 'customFieldId', 'comparator': 'EqualTo', 'value': 'FieldValue'}`). Refer to Wrike API documentation for detailed structure. | | `contractTypes` | array | No | Filters projects by contract type names; mainly used when `project` is true. | | `nextPageToken` | string | No | Token from a previous response's `nextPageToken` field for pagination; other filters should match the initial request. | | `customItemTypes` | array | No | Filters by a list of custom item type IDs (standard types like 'Project' or 'Folder' are not applicable). | | `withInvitations` | boolean | No | If true, includes invited (but not yet accepted) users in `sharedIds` of returned folders. | | `plainTextCustomFields` | boolean | No | If true, strips HTML tags from custom field values in the response. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List Task Blueprints **Slug:** `WRIKE_LIST_TASK_BLUEPRINTS` Retrieves a list of defined Task Blueprints (predefined task templates) from the Wrike account, supporting pagination. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `limit` | integer | No | The maximum number of Task Blueprints to be returned in the API response. The Wrike API enforces a maximum value of 1000 for this parameter. Default is 1000. | | `page_size` | integer | No | The number of Task Blueprints to include per page when paginating results. This parameter works in conjunction with `next_page_token`. Default is 100. | | `next_page_token` | string | No | An opaque token for fetching the next page of Task Blueprints. This token is obtained from the `nextPageToken` field in a previous API response. If omitted or empty, the first page is retrieved. Providing this token might cause the API to ignore other filter parameters. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update account metadata **Slug:** `WRIKE_MODIFY_ACCOUNT` Updates or adds custom key-value metadata to the Wrike account, useful for integrations, storing app-specific data, or mapping external system identifiers. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `metadata` | array | No | A list of metadata key-value pairs to update or add to the account. Metadata entries are isolated on a per-client (application) basis. If an empty list is provided or the field is omitted, no metadata changes will occur. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Modify folder attributes **Slug:** `WRIKE_MODIFY_FOLDER` Modifies an existing Wrike folder: updates title, description, parents (not root/recycle bin), sharing, metadata, custom fields/columns; restores, converts to project, or manages access roles. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `title` | string | No | The new title for the folder. | | `fields` | array | No | A list of optional field names to be included in the response model. NOTE: The modify folder endpoint returns all fields by default, so this parameter may have limited utility. Valid values vary by API version - check Wrike's latest documentation. | | `restore` | boolean | No | Set to true to restore the folder if it is currently in the Recycled Bin. | | `folderId` | string | Yes | Unique identifier of the folder to be modified. Must be a valid Wrike API v4 folder ID (alphanumeric string, max 256 characters). Treat as an opaque identifier - do not validate format patterns. | | `metadata` | array | No | List of metadata entries (key-value pairs) to update for the folder. | | `addParents` | array | No | Parent folder IDs to add. Must be from the same Wrike account and not be rootFolderId or recycleBinId. | | `addShareds` | array | No | A list of user IDs or invitation IDs with whom to share the folder. | | `description` | string | No | The new description for the folder. | | `customFields` | array | No | Custom fields to update or delete. Each object needs an 'id' and 'value'; pass the ID with a null value to clear. | | `customColumns` | array | No | A list of custom field IDs to be displayed as columns for this folder in the Wrike interface. | | `removeParents` | array | No | Parent folder IDs to remove. Must be from the same Wrike account and not be rootFolderId or recycleBinId. | | `removeShareds` | array | No | A list of user IDs or invitation IDs from whom to unshare the folder. | | `addAccessRoles` | object | No | User IDs mapped to Wrike access roles (e.g., 'Full', 'Editor', 'Limited', 'Read Only') to assign for this folder. Example: `{"KUAJ25LC": "Editor", "KUAJ25LD": "Full"}`. | | `withInvitations` | boolean | No | Set to true to include pending invitations in the 'ownerIds' and 'sharedIds' lists within the response. | | `removeAccessRoles` | array | No | A list of user IDs whose specific access roles for this folder should be revoked. | | `clearCustomColumns` | boolean | No | Set to true to remove all custom field column associations from this folder. | | `plainTextCustomFields` | boolean | No | Set to true to strip any HTML tags from custom field values during the update operation, saving them as plain text. | | `convertToCustomItemType` | string | No | The ID of a Custom Item Type. If provided, the folder will be converted into a project of this specified custom item type. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Modify group **Slug:** `WRIKE_MODIFY_GROUP` Updates an existing Wrike user group's attributes like title, members, parent, avatar, or metadata, using its `groupId` and specifying only the fields to change. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `title` | string | No | New title for the group. | | `parent` | string | No | ID of an existing group to set as parent for hierarchical organization. | | `groupId` | string | Yes | Unique ID of the group to modify. | | `metadata` | array | No | Custom metadata key-value pairs to update. Existing keys are updated, new ones added. To remove, set value to '"null"'. | | `addMembers` | array | No | Wrike User IDs to add to the group. Users must exist. | | `avatar__color` | string | No | New avatar background color (e.g., '#3AB795'). | | `removeMembers` | array | No | Wrike User IDs to remove from the group. | | `addInvitations` | array | No | User IDs of invited users (pending Wrike invitation) to add to the group. | | `avatar__letters` | string | No | New avatar letters for the group (max 2 chars, e.g., 'RD'). | | `removeInvitations` | array | No | User IDs of invited users to remove from the group. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Modify task **Slug:** `WRIKE_MODIFY_TASK` Modifies an existing Wrike task by its ID, allowing updates to attributes such as title, status, dates, assignees, and custom fields; `priorityBefore` and `priorityAfter` are mutually exclusive, and parent folder IDs for `addParents`/`removeParents` cannot be the Recycle Bin. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `dates` | object | No | A dictionary specifying the task's date-related attributes. Allowed keys include `type` (e.g., 'Planned', 'Actual'), `duration` (in minutes), `start` (YYYY-MM-DD), `due` (YYYY-MM-DD), and `workOnWeekends` (boolean). | | `title` | string | No | The new title for the task. | | `fields` | array | No | A list of optional field names to be included in the response object. Provide a list of strings, where each string is a valid field key. For example, `["recurrence", "responsibleIds"]`. | | `follow` | boolean | No | Set to `true` to make the current API user follow the task, or `false` to unfollow. | | `status` | string ("Active" | "Completed" | "Deferred" | "Cancelled") | No | The new status of the task. This field is not available for accounts on the Team plan. | | `taskId` | string | Yes | The unique identifier of the task to be modified. | | `restore` | boolean | No | Set to `true` to restore the task if it is currently in the Recycle Bin. | | `metadata` | array | No | A list of metadata key-value pairs to update. Providing a `null` value for an existing key's `value` will remove that entry. | | `addParents` | array | No | A list of folder IDs to which the task will be added (i.e., moved into). Cannot include the Recycle Bin folder ID. | | `addShareds` | array | No | A list of user IDs or invitation IDs with whom the task will be shared. | | `importance` | string ("High" | "Normal" | "Low") | No | The new importance level of the task. | | `billingType` | string ("NonBillable" | "Billable" | "NonBillableAddToProjectReports") | No | Specifies the billing type for the task's timelogs. | | `description` | string | No | The new detailed description for the task. Supports HTML formatting. | | `addFollowers` | array | No | A list of user IDs to be added as followers to the task. Followers receive notifications about task updates. | | `customFields` | array | No | A list of custom field updates. Each object should specify the `id` of the custom field and its new `value`. To remove a custom field's value, set `value` to `null` (or an empty string for certain types). Example: `{"id": "customFieldId123", "value": "newValue"}`. | | `customStatus` | string | No | The ID of the custom status to apply to the task. This is used when custom workflows are enabled in the Wrike account. | | `addSuperTasks` | array | No | A list of task IDs that will become parent tasks to the current task, effectively making the current task a subtask of each specified task. | | `priorityAfter` | string | No | The ID of an existing task after which the current task should be placed in the task list, determining its priority. Mutually exclusive with `priorityBefore`. | | `removeParents` | array | No | A list of folder IDs from which the task will be removed. Cannot include the Recycle Bin folder ID. | | `removeShareds` | array | No | A list of user IDs or invitation IDs from whom the task will be unshared. | | `priorityBefore` | string | No | The ID of an existing task before which the current task should be placed in the task list, determining its priority. Mutually exclusive with `priorityAfter`. | | `addResponsibles` | array | No | A list of user IDs or invitation IDs to be added to the task's assignee list. | | `withInvitations` | boolean | No | Set to `true` to include pending invitations in the `sharedIds` and `responsibleIds` fields within the response data. Default is `false`. | | `removeSuperTasks` | array | No | A list of task IDs from which the current task will be removed as a subtask. | | `removeResponsibles` | array | No | A list of user IDs or invitation IDs to be removed from the task's assignee list. | | `plainTextCustomFields` | boolean | No | Set to `true` to strip HTML tags from custom field values before saving. If `false`, HTML content is preserved. API defaults to `false` behavior if not provided. | | `convertToCustomItemType` | string | No | The ID of a Custom Item Type to which this task should be converted. This changes the task's type and may alter its available custom fields and behavior. | | `addResponsiblePlaceholders` | array | No | A list of placeholder IDs to be added to the task's placeholder assignee list. Placeholders represent roles or groups. | | `removeResponsiblePlaceholders` | array | No | A list of placeholder IDs to be removed from the task's placeholder assignee list. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Retrieve custom field by id **Slug:** `WRIKE_QUERY_CUSTOMFIELDS` Retrieves a Wrike custom field's detailed information (e.g., type, possible values for dropdowns), properties, and metadata; the `customFieldId` must correspond to an existing custom field. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `customFieldId` | string | Yes | Unique identifier of the custom field. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Query invitations **Slug:** `WRIKE_QUERY_INVITATIONS` Retrieves all active invitations in Wrike, useful for viewing and auditing pending invitations or managing user onboarding. #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Query job roles **Slug:** `WRIKE_QUERY_JOB_ROLES` Tool to retrieve all available job roles in the Wrike account. Use when you need to discover job roles or get a complete list of roles without knowing specific IDs. #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get group by id **Slug:** `WRIKE_QUERY_SPECIFIC_GROUP` Retrieves detailed information for a specific Wrike group using its `groupId`, optionally including 'metadata'. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `fields` | array | No | Specifies a list of optional fields to be included in the response. The only valid value to pass in the list is 'metadata', which will include group metadata. If omitted or an empty list is provided, a default representation of the group is returned. | | `groupId` | string | Yes | The unique identifier of the Wrike group whose details are to be retrieved. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Query workflows **Slug:** `WRIKE_QUERY_WORKFLOWS` Fetches a list of all workflows with their detailed information from the Wrike account; this is a read-only action and does not support pagination or filtering through its parameters. #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Retrieve list of groups **Slug:** `WRIKE_RETRIEVE_LIST_OF_GROUPS` Retrieves a list of user groups from the Wrike account, supporting metadata filtering, pagination, and inclusion of specific fields; this is a read-only operation. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `fields` | array | No | Optional fields to include per group; only 'metadata' (custom key-value pairs) is currently supported. Default fields are returned if omitted. | | `metadata` | object | No | Filters groups by exact match on custom metadata; keys are field IDs/names, values are expected metadata. | | `pageSize` | integer | No | Maximum group entries per page for pagination; API default applies if omitted. | | `pageToken` | string | No | Token from a previous response's 'nextPageToken' to get the next page; typically overrides other query parameters. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Search eDiscovery **Slug:** `WRIKE_SEARCH_EDISCOVERY` Tool to perform eDiscovery search across Wrike items (folders, projects, tasks). Use when you need to find items matching specific search terms across different scopes. Supports wildcard searches and filtering by item types. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `terms` | array | No | Array of search terms to look for in item titles and descriptions. Supports wildcard searches. | | `scopes` | array | No | Array of item types to search within (e.g., 'folder', 'project', 'task'). If omitted, searches all types. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update approval **Slug:** `WRIKE_UPDATE_APPROVALS` Updates an existing Wrike approval by its ID, allowing modifications to the title, description, and due date. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `dueDate` | string | No | Due date for the approval in YYYY-MM-DD format. | | `approvalId` | string | Yes | The unique identifier of the approval to be updated. | | `description` | string | No | Updated description for the approval. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update asset **Slug:** `WRIKE_UPDATE_ASSET` Tool to update a Wrike asset/equipment by ID. Use when you need to rename or modify an equipment asset in the system. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `name` | string | Yes | The updated name for the asset/equipment | | `assetId` | string | Yes | The unique identifier of the asset to update | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update attachment **Slug:** `WRIKE_UPDATE_ATTACHMENT` Tool to update a Wrike attachment by uploading new file content. Use when you need to replace an existing attachment with a new version. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `contentType` | string | No | MIME type of the file content (e.g., 'text/plain', 'application/pdf', 'image/png'). If not specified, it will be inferred from the file. | | `attachmentId` | string | Yes | The ID of the attachment to update. This is the Wrike attachment identifier (e.g., 'IEAGWTJBIYUICQ4L'). | | `file_to_upload` | object | Yes | File to upload as the new version of the attachment. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update booking **Slug:** `WRIKE_UPDATE_BOOKINGS` Updates a Wrike booking's date range by ID. Use when you need to reschedule a resource booking by modifying its start and finish dates. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `bookingId` | string | Yes | The unique identifier of the booking to update | | `bookingDates` | object | Yes | Updated booking date range with start and finish dates | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update comment **Slug:** `WRIKE_UPDATE_COMMENT` Tool to update an existing Wrike comment. Use when you need to modify the text content of a comment. Supports HTML formatting with limited tags. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `text` | string | Yes | Updated comment text. Supports HTML format with limited tags. Use when you need to modify the content of an existing comment. | | `commentId` | string | Yes | The unique identifier of the comment to update | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update custom field by id **Slug:** `WRIKE_UPDATE_CUSTOM_FIELD_BY_ID` Updates properties of an existing Wrike custom field by its ID, such as its title, type, scope, or sharing settings. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `type` | string | No | New type for the custom field. Changing this can affect existing data. | | `title` | string | No | New title for the custom field. | | `sharing` | object | No | Defines access settings, superseding `addShareds` and `removeShareds`. Expected format is an array of objects, e.g., `[{"accessorId": "ID", "accessType": "ReadOnly \| ReadWrite"}]`. | | `spaceId` | string | No | ID of the Space. Required if `changeScope` is 'AccountToSpace' or when changing a space-level custom field's space association. | | `settings` | object | No | Settings specific to the custom field type, e.g., list values for 'DropDown', decimal places for 'Numeric'. Structure varies by 'type'. | | `addMirrors` | array | No | List of custom field IDs to add as mirrors. Applicable only to 'LinkToDatabase' custom fields. | | `addShareds` | array | No | Obsolete: Use the `sharing` parameter instead. | | `changeScope` | string | No | Specifies if the custom field's scope should change. Use 'AccountToSpace' (requires `spaceId`) to convert an account-level field to space-level, or 'SpaceToAccount' to convert a space-level field to account-level. | | `customFieldId` | string | Yes | Identifier of the custom field to be updated. | | `removeMirrors` | array | No | List of custom field IDs to remove as mirrors. Applicable only to 'LinkToDatabase' custom fields. | | `removeShareds` | array | No | Obsolete: Use the `sharing` parameter instead. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update dependency **Slug:** `WRIKE_UPDATE_DEPENDENCY` Tool to modify an existing Wrike dependency relationship between tasks. Use when you need to update the dependency type or change which tasks are linked. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `successorId` | string | No | The task ID that depends on the predecessor | | `dependencyId` | string | Yes | The unique identifier of the dependency to modify | | `relationType` | string ("FinishToStart" | "FinishToFinish" | "StartToStart" | "StartToFinish") | No | Enum for dependency relation types. | | `predecessorId` | string | No | The task ID that must be completed first | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update folder rollup settings **Slug:** `WRIKE_UPDATE_FOLDERS_ROLLUPS` Tool to update rollup settings for a folder. Use when you need to enable or disable field aggregation from descendant items. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `rollups` | array | Yes | Array of rollup settings to update. Each item specifies a fieldId and whether rollup should be enabled for that field. | | `folderId` | string | Yes | The unique identifier of the folder for which to update rollup settings. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update invitation **Slug:** `WRIKE_UPDATE_INVITATION` Updates a pending Wrike invitation (`invitationId`) to resend it or change user's role/type (use EITHER `userTypeId` OR `role`/`external`). #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `role` | string ("Collaborator" | "User") | No | User's role (e.g., 'User', 'Collaborator'). Mutually exclusive with 'userTypeId'. | | `resend` | boolean | No | Resends the invitation email if true. | | `external` | boolean | No | Marks user as external. Requires 'role' to be 'User'. Mutually exclusive with 'userTypeId'. | | `userTypeId` | string | No | ID of the user type to assign. Mutually exclusive with 'role' and 'external'. | | `invitationId` | string | Yes | Unique identifier of the invitation to modify. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update job role **Slug:** `WRIKE_UPDATE_JOB_ROLE` Updates an existing Wrike job role by its ID, allowing modifications to the title and short title. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `title` | string | No | New title for the job role. | | `jobroleId` | string | Yes | Unique identifier of the job role to be updated. | | `shortTitle` | string | No | New short title for the job role. Must be 0-2 characters. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update metadata on a specific contact **Slug:** `WRIKE_UPDATE_METADATA_ON_SPECIFIC_CONTACT` Updates metadata, job role, or custom fields for an existing Wrike contact specified by `contactId`; if `jobRoleId` is provided, it must be a valid ID. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `fields` | array | No | Optional list of field names to include in the response. If provided, only these fields will be returned. | | `metadata` | array | No | List of metadata key-value pairs to update. Users typically have read/write access to their own metadata; other entries may be read-only. | | `contactId` | string | Yes | Unique identifier of the contact to update. | | `jobRoleId` | string | No | Unique identifier of the job role to assign, which updates the contact's current role. | | `customFields` | array | No | List of custom field updates. Each item should specify the custom field and its new value. Providing a null value might remove the custom field, depending on API behavior. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update a specific user **Slug:** `WRIKE_UPDATE_SPECIFIC_USER` Updates specified profile attributes (e.g., account ID, role, external status) for an existing Wrike user; unspecified fields remain unchanged. Note: The current API user can only update users they have permission to modify. Account owners, robot users, and the current user themselves typically cannot be modified. This action requires the 'amReadWriteUser' OAuth scope. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `active` | boolean | No | Set to true to activate the user or false to deactivate the user account. | | `userId` | string | Yes | Unique identifier for the user whose profile is to be updated. Must be a valid Wrike user ID (8-character alphanumeric string). | | `userTypeId` | string | No | ID of the user type to assign. Cannot be used together with profile parameters. | | `profile__role` | string | No | Role to assign to the user's profile. Common values: 'User', 'Collaborator'. | | `profile__external` | boolean | No | Indicates if the user is an external user. | | `profile__accountId` | string | No | Unique identifier of the account to associate with the user's profile. Required when updating profile fields. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update task rollup settings **Slug:** `WRIKE_UPDATE_TASKS_ROLLUPS` Updates rollup settings for a task. Rollup settings control how field values aggregate from child tasks to parent tasks. Use this when you need to enable or disable automatic rollup calculations for specific fields like start dates, due dates, or custom fields. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `taskId` | string | Yes | The unique identifier of the task to update rollup settings for. | | `rollups` | array | Yes | Array of rollup setting objects to update. Each object specifies a field ID and whether rollup is enabled for that field. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update timelog entry **Slug:** `WRIKE_UPDATE_TIMELOGS` Tool to modify an existing timelog entry in Wrike. Use when you need to update the hours, comment, tracked date, or category of a time log. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `hours` | number | No | Number of hours tracked for this timelog entry. Must be a positive decimal value. | | `comment` | string | No | Comment or description for the timelog entry. Provide updated text to replace the existing comment. | | `plainText` | boolean | No | Set to true to strip HTML tags from the comment field, saving it as plain text. If false or not provided, HTML formatting is preserved. | | `timelogId` | string | Yes | The unique identifier of the timelog entry to update. | | `categoryId` | string | No | ID of the timelog category to assign to this entry. Use this to categorize time entries (e.g., 'Development', 'Meeting', 'Documentation'). | | `trackedDate` | string | No | Date when the work was performed, in ISO 8601 format (YYYY-MM-DD). If not specified, the existing tracked date remains unchanged. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update timesheet row **Slug:** `WRIKE_UPDATE_TIMESHEET_ROW` Updates a Wrike timesheet row by its ID, allowing modification of the timelog category. Use when you need to change the time tracking category for a timesheet entry. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `categoryId` | string | No | The timelog category ID to assign to the timesheet row. Use this to change the time tracking category for a timesheet entry. | | `timesheet_rowId` | string | Yes | The unique identifier of the timesheet row to update. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update timesheet **Slug:** `WRIKE_UPDATE_TIMESHEETS` Tool to update a timesheet's approval status in Wrike. Use when you need to submit, approve, or reject a timesheet. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `timesheetId` | string | Yes | The unique identifier of the timesheet to update. | | `approvalStatus` | string ("Pending" | "Approved" | "Rejected") | Yes | Approval status to set for the timesheet. Use 'Pending' when the timesheet owner submits for approval, 'Approved' when approving, or 'Rejected' when declining. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update webhook state **Slug:** `WRIKE_UPDATE_WEBHOOK_STATE` Tool to update the state of a Wrike webhook. Use when you need to re-enable a suspended webhook or suspend an active one. Wrike automatically suspends webhooks after 3 failed delivery attempts. Call this with status=Active to re-enable. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `status` | string ("Active" | "Suspended") | Yes | Webhook state to set. Use 'Active' to re-enable a suspended webhook, or 'Suspended' to disable it | | `webhookId` | string | Yes | The unique identifier of the webhook to update | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update workflow **Slug:** `WRIKE_UPDATE_WORKFLOW` Tool to modify an existing Wrike workflow. Use when you need to update a workflow's name or description. Requires amReadWriteWorkflow scope. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `name` | string | No | New name for the workflow | | `workflowId` | string | Yes | The unique identifier of the workflow to modify | | `description` | string | No | New description for the workflow | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update work schedule timesheet rules **Slug:** `WRIKE_UPDATE_WORKSCHEDULE_TIMESHEET_RULES` Tool to update timesheet submission rules for a work schedule. Use when you need to configure or modify how timesheet submissions are validated and enforced for a specific work schedule. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `enabled` | boolean | No | Whether timesheet submission rules are enabled for this work schedule. Set to true to activate rules or false to disable them. | | `frequency` | string ("Day" | "Week") | No | Enum for timesheet submission frequency values. | | `rule_type` | string ("Hard" | "Soft") | No | Enum for timesheet submission rule type values. | | `workschedule_id` | string | Yes | The ID of the work schedule to update timesheet submission rules for. | | `track_exceptions_mode` | string ("ActualCapacity") | No | Enum for track exceptions mode values. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not |