> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-cloud-runtime-security/cortex-cloud-data-sources-and-connectors/vendor-specific-data-sources/wrike.md).

# Wrike

Use Wrike data with Cortex Cloud.

The capabilities and sub-capabilities listed for this connector are available with any active Cortex XSIAM or Cortex Cloud Posture Security license.

This connector includes the following capabilities and sub-capabilities (if applicable):

* **SaaS Posture Configuration Monitoring:** Detect, monitor and alert on settings of your SaaS application.
  * **saas-posture-config-remediation:** Help remediate the misconfigured security settings of your SaaS application.

### How to configure the Wrike connector

To access Wrike, Cortex Cloud requires the following information, which you will specify during the connection process.

* **Permanent Access Token:** A long-lived API token generated from the Wrike API console. Cortex Cloud uses this token to authenticate to the Wrike API.

Perform the following procedures in the order that they appear below.

#### Task 1: Generate a Wrike Permanent Access Token

1. Log in to your Wrike account at <https://www.wrike.com>.
2. In the left sidebar, click your profile, then click **Apps & Integrations**.
3. Click the **API** tab. Wrike redirects you to the API console.
4. Click **+ App** to create a new app.
5. Enter an **App Name** and **Description**, then click **Create**.
6. Scroll down to the **Permanent access token** section and click **Get token**.
7. Enter your Wrike account password and click **Get token**.
8. Copy the generated token immediately and store it securely in a text file.

   > The token is shown only once. You cannot retrieve it after you navigate away from this page. You must provide this value to Cortex Cloud during the onboarding process.
9. Click **Save** to save the app.

#### Task 2: Connect Wrike to Cortex Cloud

1. In Cortex Cloud, navigate to **Settings** → **Data Sources & Integrations**.
2. Click **+ Add new**.
3. In the **Add Data Source** page, search for Wrike.
4. Under **Recommended**, hover over the new Wrike integration and click **Add Instance** to launch the configuration wizard.
5. Under the **Capabilities** tab, enter a name for your application.
6. Select **Security Posture** under **Default Capabilities**. Click **Next**.
7. Under the **Connection** tab, enter the **Permanent Access Token** details.
8. Under the **Configuration** tab, select a **Sync Interval**. Choose a meaningful **Tag** to distinguish between various applications in different environments.
9. A confirmation message shows that Wrike is successfully connected. Confirm the **Summary** details and click **Save instance**.


---

# 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://cortex-docs.paloaltonetworks.com/cortex-cloud-runtime-security/cortex-cloud-data-sources-and-connectors/vendor-specific-data-sources/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.
