Claude Wrike connectorWhat Claude can do in your Wrike account.
The Claude Wrike connector exposes 28 tools. 17 read your spaces, tasks, comments, forms and approvals, 10 create or change work, and 1 is listed with no matching description. Here: what Claude does, what it asks, and who controls it.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when Claude can reach your Wrike
You stop clicking through folders to find out where a project stands. You ask Claude, it searches your spaces, reads the details and the comment threads, and answers in the conversation. When the answer calls for action, it can create the tasks, post the comment or file the request itself, within your own Wrike permissions.
Meeting notes that turn into assigned work. Paste the notes, and create_task_item creates each action item with its owner, dates and status, nested under the right parent if needed.
A morning triage in one question. get_my_inbox goes through unread mentions, assignments and status changes, search_approvals adds what is waiting on your sign-off, and Claude tells you what needs you first.
Work intake the way your teams expect it. search_requestforms finds the right form, get_requestform shows its fields, and submit_requestform files it, which creates the task or project that form is set up for. For recurring projects, create_item_from_blueprint starts from the team template.
Now what it does not do. Claude sees only what the connected Wrike user sees, and one bulk edit touches 20 items at most. Nothing runs by itself: no tool fires when a status changes or a due date passes. For that kind of background job, look at the Wrike Make integration, a different trade.
The vocabulary in one minute
Five words you will meet while plugging Wrike in.
- Connector
- The link you set up once between Claude and an account you already have, so it can work in that account while it answers you.
- Tool
- One named action a connector opens to Claude. Claude picks the ones it needs by itself; the directory sheet lists them by name.
- Authorization
- The service's own sign-in screen, where you hand Claude the access it will use. Given once per person, and you can take it back.
- Approval
- The confirmation Claude waits for before it goes through with something that changes your account. Not to be confused with Wrike's own sign-offs.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as Wrike.
Plug Wrike into Claude in three steps
- 01
Find Wrike in Claude
In Claude's settings, open Customize, then Connectors, and look for Wrike in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to switch the connector on first, then each member connects on their own.
- 02
Start the connection
Click Connect on its row and sign in to Wrike in the window Wrike opens itself. If the link breaks later, use Disconnect and plug it back in from the same row.
- 03
Read the authorization screen
Read the screen before you accept. It belongs to Wrike, not to Claude, and it sets what the access covers. You can withdraw that access later from your Wrike account as well.
The 28 Claude Wrike connector tools, grouped by what they do
Wrike gives Claude 28 tools: 17 that read your account, 10 that change something in it, and 1 no official source describes.
Three groups: what Claude reads, what it changes, and what no official source describes. The names stay exactly as Claude shows them.
- 17 read
- 10 write
- 1 not documented
What Claude reads (17)
17 toolsTools that look at your spaces, items, people, forms and approvals without touching them.
get_item_comments
Reads the full comment thread of an item, with the author and time of each message, so Claude can sum up a long discussion.
get_item_details
Pulls the full picture of up to five items at once: status, custom fields, assignees and attachments, linked external files included.
get_my_inbox
Goes through your unread Wrike notifications, mentions, assignments, new statuses and replies, so Claude can tell you what needs you first.
get_users
Finds specific people by ID or email, or works out who "me" is, which Claude needs before it assigns or filters by person.
search_customitemtypes
Finds a custom item type, such as a Campaign or a Bug, and its ID, ranked by how often your workspace uses it.
search_item_customfields
Looks up custom fields by name, with their type and, for dropdowns, the list of allowed options, so a filter uses values that actually exist.
search_items
Searches tasks, folders and projects by keyword, with filters on assignee, status, dates and importance, and can stay inside one space or branch.
search_users
Finds people or groups by name, and with no name at all brings up the collaborators you work with most, a handy shortcut when you do not remember how a colleague spells their name.
search_workflows
Finds workflows, the sequence of statuses work goes through, and their custom statuses, with the status IDs Claude needs to filter by status or set one.
get_approvals
Looks up approvals by ID or lists those attached to an item, with their status, approvers and decisions, so a stalled sign-off has a name on it.
search_approvals
Filters approvals across the whole workspace by status, approver and due date, which turns a vague feeling that things are stuck into a list with names and dates.
get_items_children
Walks the hierarchy one level at a time, from a space down to its folders, projects and tasks, which keeps large workspaces navigable.
search_spaces
Lists the spaces you belong to, or filters them by name, which is usually where Claude starts in an unfamiliar workspace.
search_blueprints
Looks for reusable Wrike blueprints, the templates a team keeps for recurring kinds of work, so Claude starts from what your colleagues already built rather than from scratch.
search_requestforms
Queries the request forms available in Wrike, the intake forms teams use to receive work in a structured way, so a request lands where the receiving team expects it.
get_requestform
Retrieves the pages, fields, options and rules of an existing request form, so Claude knows which information is required before anything gets filled in.
prefill_requestform
Generates a link to a request form with some values already filled in. Wrike is explicit: it neither submits the form nor creates any item.
What Claude changes (10)
10 toolsTools that create, edit, attach, comment or submit. No source gives any of them its own confirmation rule: the general rule below applies.
create_item_comment
Approval: see the rulePosts a comment on any task, folder or project, and can @-mention teammates in it.
create_project_folder_item
Approval: see the ruleSets up folders and projects, optionally from a custom item type, with owners, dates and status already filled in.
create_task_item
Approval: see the ruleCreates one task or many, with assignee, dates, duration and status, and can nest them as subtasks under a parent.
update_items
Approval: see the ruleEdits title, description, status, dates and custom fields, adds or removes assignees and parents, converts an item's type, and can apply one change to up to 20 items at once.
prepare_attachment_upload
Approval: see the ruleUploads a file into Wrike so it can be attached to a work item in a second step.
add_attachments_to_item
Approval: see the ruleAttaches to a work item a file that was uploaded with prepare_attachment_upload, completing the two-step attachment.
create_item_from_blueprint
Approval: see the ruleCreates a new task, folder, project, custom item or a whole tree of items from an existing blueprint.
submit_requestform
Approval: see the ruleSubmits a request form, which creates the task or project that form is set up to produce.
add_whiteboard_to_item
Approval: see the ruleLinks an existing whiteboard to a work item, so the visual work sits next to the task it belongs to.
remove_whiteboard_from_item
Approval: see the ruleRemoves a whiteboard from a work item. Wrike's description says it takes the board off the item, without saying anything about the board itself.
Undocumented (1)
1 toolThe directory lists this name and Wrike's pages describe none spelled exactly like it. The page does not guess what it does.
get_asyncjob
This name sits on the directory sheet, but Wrike's tool pages describe a similarly spelled status tool under a different name, with an extra underscore. No official source documents this exact spelling, so the page reads nothing into it.
What Claude asks before it acts
By default, Claude stops and asks for your go-ahead before each action it carries out on an account for you. The request shows up in the conversation, at the moment it matters.
On a Team or Enterprise workspace, owners decide whether a member may let some actions through without being asked every time. They can also limit what a connector may do for the whole organisation, keeping search open and closing writing, for example; Wrike's own setup guide tells admins to configure those tool permissions when they add the connector. That setting applies to everyone. And Claude inherits the rights of the connected Wrike user: a project you cannot open in Wrike stays closed to it too.
Which plans it is available on
None of the 819 directory sheets shows availability by plan. The answer, connector by connector, is not published anywhere: it is a real gap in the catalogue.
The general rule is published, though. Remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner opens the connector for the organisation before members can connect individually. For the current state, check Wrike's sheet in the official directory. One more point: this connector is documented only by Wrike itself, with no Claude help page of its own.
Where the Claude Wrike connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing starts when a task changes status, a form comes in or a deadline passes.
The tool list is an observed floor, not a promise: an administrator can open actions that appear on no public sheet. The directory's partner badge is not a security audit either, and Anthropic says so on every sheet: it does not choose the tools a publisher exposes and does not guarantee they behave as announced. Plug in only what comes from a publisher you trust. Wrike adds that the same question can get slightly different answers from one run to the next, and that naming the project, folder or task link helps. Other connectors are gathered on the Integrations hub.
How many tools does the Wrike connector expose?
- Wrike connector sheet in Claude's directory ↗September 2026The sheet lists 28 named tools.
- Wrike's "Available tools" page, opening lines ↗September 2026Out of dateWrike opens by announcing 17 tools in total, 4 of which make changes.
What this page followsWrike's opening count clashes with its own tables further down the same page, which describe 28 tools, 10 of them making changes. The directory sheet and those tables agree, so this page follows them: 28 tools. No source explains the gap, so do not rely on the short count.
Need help connecting Wrike to Claude?
A person reads every message.
