> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/integrations/catalog/wrike.md).

# Wrike

Wrike is a project management and work collaboration platform. Connect to manage folders, projects, tasks, and comments from your AI workflows.

## Connectors

Choose the connector that matches your authentication method. The options below use the names shown in StackAI.

| Connector | Authentication |
| --------- | -------------- |
| Wrike     | Credentials    |

### Wrike

Connect to Wrike with a permanent access token to manage folders, projects, tasks, and comments.

#### Set up in Wrike

1. Sign in to Wrike, open your avatar menu, and go to **Apps & Integrations → API** (or visit the [Wrike App Directory API page](https://www.wrike.com/frontend/apps/index.html#/api)).
2. Create a new API app (any name works; it's only visible to you), open it in the App Console, and click **Get token**. Confirm with your password.
3. Copy the permanent access token when it appears; it is shown only once. Treat it like a password: it grants access as your Wrike user.

#### Set up in StackAI

1. Open **Settings → Connections**, add a connection, and select **Wrike**.
2. Enter the credentials and connection details in the fields below.
3. Save the connection and check its connection status. Select this saved connection when configuring an action or feature that uses it.

**Connection fields**

| StackAI field          | Required | What to enter                                                                                                                                                                                                                                                 |
| ---------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Wrike URL              | Yes      | The URL you see in your browser when signed in to Wrike, e.g. <https://www.wrike.com> or <https://app-us2.wrike.com>. Wrike hosts accounts in different data centers, so this must match your account's host. [Provider instructions](https://www.wrike.com). |
| Permanent Access Token | Yes      | A Wrike permanent access token. Create one in Wrike under Apps & Integrations > API > Permanent access token. [Provider instructions](https://www.wrike.com/frontend/apps/index.html#/api).                                                                   |

**Provider documentation:** [Setup reference](https://developers.wrike.com/oauth-20-authorization/).

### Verify the connection

Check that the connection is healthy. Then run a read operation against a resource the connected account can access. A successful connection check confirms authentication; it does not guarantee permission for every action.

If access is denied, check the credential or OAuth permissions, the selected account or environment, and access to the specific resource. Update expired credentials or reconnect after permissions change.

## Use an action

1. Add the required **Wrike** action to the workflow.
2. Select a connection when the action requests one.
3. Complete the required fields. Use the reference picker when a value comes from another workflow step.
4. Run the workflow and inspect the action’s output. Check the result before using it in a later step.

## Actions

### Create Task

Create a new task in a Wrike folder or project.

#### Inputs

| Field            | Type            | Required | Description                                                                                   |
| ---------------- | --------------- | -------- | --------------------------------------------------------------------------------------------- |
| Folder / Project | string          | Yes      | The folder or project to create the task in.                                                  |
| Title            | string          | Yes      | The task title.                                                                               |
| Description      | textarea        | No       | Optional task description.                                                                    |
| Status           | select (string) | No       | Initial status. Defaults to Active. Available values: Active, Completed, Deferred, Cancelled. |
| Importance       | select (string) | No       | Task importance. Defaults to Normal. Available values: High, Normal, Low.                     |

#### Outputs

| Field     | Type   | Description                       |
| --------- | ------ | --------------------------------- |
| Task ID   | string | The created task's ID.            |
| Title     | string | The created task's title.         |
| Permalink | string | A link to open the task in Wrike. |
| Status    | string | The task's status.                |

### Query Tasks

List Wrike tasks, optionally filtered by folder, title, and status.

#### Inputs

| Field            | Type            | Required | Description                                                                       |
| ---------------- | --------------- | -------- | --------------------------------------------------------------------------------- |
| Folder / Project | string          | No       | Optional folder or project to list tasks from.                                    |
| Title contains   | string          | No       | Optional text to match within task titles.                                        |
| Status           | select (string) | No       | Optional status filter. Available values: Active, Completed, Deferred, Cancelled. |

#### Outputs

| Field    | Type        | Description                                              |
| -------- | ----------- | -------------------------------------------------------- |
| Tasks    | dict\_array | The matching tasks.                                      |
| Count    | integer     | Number of tasks returned (may be capped; see has\_more). |
| Has More | boolean     | True if more tasks exist beyond the returned set.        |

### Update Task Status

Change the status of an existing Wrike task.

#### Inputs

| Field  | Type            | Required | Description                                                               |
| ------ | --------------- | -------- | ------------------------------------------------------------------------- |
| Task   | string          | Yes      | The task to update.                                                       |
| Status | select (string) | Yes      | The new status. Available values: Active, Completed, Deferred, Cancelled. |

#### Outputs

| Field   | Type   | Description                         |
| ------- | ------ | ----------------------------------- |
| Task ID | string | The updated task's ID.              |
| Status  | string | The task's status after the update. |

### Add Comment to Task

Add a comment to a Wrike task.

#### Inputs

| Field   | Type     | Required | Description             |
| ------- | -------- | -------- | ----------------------- |
| Task    | string   | Yes      | The task to comment on. |
| Comment | textarea | Yes      | The comment text.       |

#### Outputs

| Field        | Type   | Description                        |
| ------------ | ------ | ---------------------------------- |
| Comment ID   | string | The created comment's ID.          |
| Task ID      | string | The task the comment was added to. |
| Comment Text | string | The comment text as stored.        |

### Create Folder or Project

Create a folder or project inside a Wrike folder.

#### Inputs

| Field             | Type     | Required | Description                                                 |
| ----------------- | -------- | -------- | ----------------------------------------------------------- |
| Parent Folder     | string   | Yes      | The folder to create the new folder/project inside.         |
| Title             | string   | Yes      | The name of the folder or project.                          |
| Description       | textarea | No       | Optional description.                                       |
| Create as project | boolean  | No       | Create a project instead of a plain folder. Default: false. |

#### Outputs

| Field      | Type    | Description                                 |
| ---------- | ------- | ------------------------------------------- |
| Folder ID  | string  | The created folder/project's ID.            |
| Title      | string  | The created folder/project's title.         |
| Permalink  | string  | A link to open the folder/project in Wrike. |
| Is Project | boolean | True if the created item is a project.      |

## Important behavior

Actions that create, update, send, or delete data can change the connected service. Review their inputs before running them. A retry can repeat an operation; consider this when configuring retries for actions that change data.

The catalog lists the fields and capabilities available in the supplied provider definition. Availability can also depend on your deployment and organization’s Feature Access settings.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/integrations/catalog/wrike.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
