> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gradial.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Wrike Integration

> Connect Gradial to Wrike to automatically ingest tasks and sync results — previews, links, and status updates — back to Wrike.

**What you can do:**

* Automatically ingest Wrike tasks into Gradial workflows
* Filter by space, folder, status, or custom fields to control what gets executed
* Attach source documents directly to Wrike tasks for context
* Write previews, links, and status updates back to Wrike
* Standardize execution pipelines across teams

***

## Prerequisites

**What you'll need:**

* Your **Wrike domain** (e.g., `https://app.wrike.com`)
* A **Wrike service account** — a dedicated user that Gradial acts through
  * Must have access to the spaces, folders, and projects you want to sync
  * Should be set as the **first assignee** on any task you want Gradial to process
* A **Personal Access Token (PAT)** generated by the service account
* A designated **custom team field** for task routing (e.g., "Gradial Team") — must be a short-text field

***

## Authentication options

| Method                          | Requirements                                                                                   |
| ------------------------------- | ---------------------------------------------------------------------------------------------- |
| **Personal Access Token (PAT)** | Token generated from the service account's Wrike profile → Apps & Integrations → Access Tokens |

***

## Connect Wrike to Gradial

Go to **Integrations** in the Gradial sidebar, select **Wrike**, and click **Add Integration**.

1. Enter your **Wrike domain**
2. Enter the **service account email** in the Assignee field
3. Enter the **custom team field** label exactly as it appears in Wrike (e.g., `Gradial Team`)
4. Generate a PAT: log in as the service account → profile settings → **Apps & Integrations → Access Tokens → Create new token**
5. Paste the token into **Personal Access Token**
6. Optionally add filters to limit which tasks Gradial ingests (see below)
7. Click **Save**

**Optional filters:**

| Filter            | Description                                |
| ----------------- | ------------------------------------------ |
| **Projects**      | Limit to specific project keys or folders  |
| **Statuses**      | e.g., `In Progress`, `Ready for Execution` |
| **Custom fields** | e.g., task type or priority                |

***

## Configure routes

Once connected, create routes to define which Wrike tasks sync into which Gradial workspaces. Wrike supports filtering by space, folder, and status.

[Configure Routes →](/docs/integrations-administration-and-setup/how-gradial-works-with-ticketing-systems/routing-tickets)

***

## How task execution works

Once integrated, the typical flow is:

1. A team member creates a task in a configured Wrike folder with a clear title and any attached reference files
2. The task is assigned to the Gradial service account and set to `In Progress`
3. Gradial ingests the task and executes the request
4. Previews, links, and comments are written back to the Wrike task
5. Task status updates automatically as execution progresses

***

## Troubleshooting

| Issue                       | Likely cause                              | Fix                                                                      |
| --------------------------- | ----------------------------------------- | ------------------------------------------------------------------------ |
| Tasks not being ingested    | Service account not set as first assignee | Ensure the Wrike service account is the primary assignee on target tasks |
| Authentication fails        | Invalid or expired PAT                    | Regenerate the token from the service account's Wrike settings           |
| Wrong tasks ingested        | Filters too broad                         | Narrow filters by project, status, or custom field                       |
| Custom field not recognized | Field name mismatch                       | Confirm the Team Field value matches the exact label in Wrike            |

Contact your Gradial onboarding lead or email [support@gradial.com](mailto:support@gradial.com) if issues persist.