Sanaf AI
Start free
Project Management

Wrike, worked by an AI employee

Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your Wrike account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.

  • Project Management
  • Signs in to your account
  • 38 ready-made tools
  • Asked in Slack or Teams
At work

An illustration of how the conversation reads, not a transcript from a client account.

What Wrike is

Wrike is a project management and collaboration tool offering customizable workflows, Gantt charts, reporting, and resource management to boost team productivity

You sign in with your own Wrike account, the same way you already do. We never see or hold your password.

How a run works

One message in, the work done in Wrike.

  1. 01

    You ask

    You message your AI employee in the chat your team already has open, in one sentence, in your own words.

  2. 02

    It works out the step

    It decides what the job needs in Wrike. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own Wrike account, inside the access you granted it, doing the thing you asked for.

  4. 04

    It reports back

    It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.

38 tools it already has

What it can do in Wrike

These are the ready-made tools your AI employee already has in Wrike. It is not limited to them, but it never has to be taught these.

  • Bulk modify group membersAdds or removes members for multiple wrike groups in a single request; all specified user ids must correspond to existing wrike users.
  • Create a folderCreates a new wrike subfolder within the specified folderid, optionally as a project if customitemtypeid is given; the folder is auto-shared with its creator.
  • Create a groupCreates a new user group in wrike with a specified title, optionally setting members, parent group, avatar, and custom metadata.
  • Create invitationInvites 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
  • Create task in folderCreates 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.
  • Delete custom field by idPermanently deletes a custom field by its id; this action is irreversible and requires a valid, existing custom field id.
  • Delete folderPermanently 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 fo
  • Delete group by idPermanently deletes a group by its groupid; this action is irreversible and does not affect user accounts that were members of the group.
  • Delete invitationPermanently deletes an existing invitation, specified by its unique invitationid; this action cannot be undone.
  • Delete taskPermanently deletes a wrike task and all its associated data by its id; this action is irreversible and the task must exist.
  • Fetch all tasksFetches tasks from a wrike account, allowing filtering by status, due date, and subfolder inclusion, with customizable response fields and pagination.
  • Get account informationRetrieves detailed wrike account information, where the response content is influenced by selected fields, account subscription, and user permissions.
  • Get all custom fieldsRetrieves 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
  • Get contactsRetrieves a list of wrike contacts (e.g., team members, clients, collaborators); response includes contact details but not their detailed task or project involvement.
  • Get foldersRetrieves folders and/or projects from wrike, with filters; when using nextpagetoken, all other filter parameters must match the initial request.
  • Get group by idRetrieves detailed information for a specific wrike group using its groupid, optionally including 'metadata'.
  • Get specific contact informationRetrieves detailed information for a specific wrike contact using their unique contactid, optionally including metadata and customfields if specified in the fields parameter.
  • Get specific userRetrieves detailed information about a specific user in wrike using their unique user id.
  • Get task by idRetrieves read-only detailed information for a specific wrike task by its unique id, optionally allowing specification of fields to include in the response.
  • Launch folder blueprint asyncAsynchronously launches a new project or folder structure in wrike from a specified folder blueprint, typically returning a task id to track progress.
  • Launch Task Blueprint AsyncAsynchronously launches a wrike task blueprint to create tasks/projects, requiring either super task id (parent task) or parent id (parent folder/project) for placement.
  • List Folder BlueprintsRetrieves all account-level folder blueprints, which are templates for standardizing folder/project creation with predefined structures, custom fields, and workflows.
  • List space folder blueprintsLists all folder blueprints (templates for new folders/projects) within a specified wrike space, requiring a valid and accessible space id.
  • List space task blueprintsLists task blueprints (templates for creating tasks with consistent structures) available in a specific, accessible wrike space.
  • List subfolders by folder idLists subfolders (metadata only, not their contents) for an existing wrike folder specified by folderid, supporting recursive descent, filtering, and pagination.
  • List Task BlueprintsRetrieves a list of defined task blueprints (predefined task templates) from the wrike account, supporting pagination.
  • Modify folder attributesModifies an existing wrike folder: updates title, description, parents (not root/recycle bin), sharing, metadata, custom fields/columns; restores, converts to project, or manages a
  • Modify groupUpdates an existing wrike user group's attributes like title, members, parent, avatar, or metadata, using its groupid and specifying only the fields to change.
  • Modify taskModifies 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
  • Query invitationsRetrieves all active invitations in wrike, useful for viewing and auditing pending invitations or managing user onboarding.
  • Query workflowsFetches 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 paramete
  • Retrieve custom field by idRetrieves 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
  • Retrieve list of groupsRetrieves a list of user groups from the wrike account, supporting metadata filtering, pagination, and inclusion of specific fields; this is a read-only operation.
  • Update a specific userUpdates specified profile attributes (e.g., account id, role, external status) for an existing wrike user; unspecified fields remain unchanged.
  • Update account metadataUpdates or adds custom key-value metadata to the wrike account, useful for integrations, storing app-specific data, or mapping external system identifiers.
  • Update custom field by idUpdates properties of an existing wrike custom field by its id, such as its title, type, scope, or sharing settings.
  • Update invitationUpdates a pending wrike invitation (invitationid) to resend it or change user's role/type (use usertypeid over deprecated role/external).
  • Update metadata on a specific contactUpdates metadata, job role, or custom fields for an existing wrike contact specified by contactid; if jobroleid is provided, it must be a valid id.
Access, and who is in charge of it

You stay the boss of your Wrike account.

Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.

How we handle your data
  • It signs in to your own Wrike account. You are not moving anything into ours.
  • You grant access one app at a time, and you can take it back the same way.
  • Everything it does in Wrike is written down, with what it did and when.
  • Anything you tell it to check with you first, it checks with you first.
Other apps in the same corner of the business

It works in Wrike and the rest of your software in the same job

A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.

See every app

Questions people ask about Wrike

Can an AI employee really work inside Wrike?
Yes. It signs in to your own Wrike account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
Do I have to move anything out of Wrike?
No. Nothing moves and nothing is replaced. Your records stay in Wrike, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
How does it get into my Wrike account?
You sign in with your own Wrike account, the same way you already do. We never see or hold your password. You approve it before anything connects, and you can take the access back the same way you gave it.
What can it actually do in Wrike?
It has 38 ready-made tools in Wrike today, among them Bulk modify group members, Create a folder and Create a group. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use Wrike and the rest of my software in the same job?
Yes, and that is usually the point. Reading a message in one app, checking a record in Wrike and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
Who decides what it is allowed to do in Wrike?
You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in Wrike is written down with what it did and when.