> 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-xsiam/cloud-security/cortex-cloud-ai-security/cortex-cloud-saas-security/onboard-a-supported-saas-application/onboard-wrike.md).

# Onboard Wrike

SaaS Security connects to Wrike using OAuth 2.0 authorization. Before onboarding, you create an OAuth 2.0 integration app in Wrike. During onboarding, SaaS Security redirects you to Wrike to log in and grant access.

Onboarding consists of two tasks:

1. Collect credentials for accessing your Wrike instance
2. Connect SaaS Security to Wrike

The onboarding process requires the following credentials:

| Item          | Description                                                                                           |
| ------------- | ----------------------------------------------------------------------------------------------------- |
| Client ID     | Generated by Wrike to uniquely identify the OAuth 2.0 integration app you create.                     |
| Client Secret | Generated by Wrike; used by SaaS Security to authenticate to the integration app.                     |
| Email ID      | The login email address of the Wrike Account Administrator who created the OAuth 2.0 integration app. |

***

#### Task 1 — Collect Information for Accessing Your Wrike Instance

**Step 1 — Get the redirect URL from Cortex**

Before creating your OAuth 2.0 integration app in Wrike, retrieve the redirect URL that SaaS Security requires.

1. Log in to [Cortex](https://cortex.paloaltonetworks.com).
2. Select **Settings > Data Sources and Integrations > Add New** and click the Wrike tile.
3. On the **Capabilities** tab, enter a name for this instance.
4. Under Default Capabilities, confirm Security Posture is selected.
5. Click Next.
6. On the **Connections** tab, the Redirect URL value is displayed.
7. Copy the redirect URL and save it to a text file.

**Note**: Do not complete the onboarding flow yet. Return to the Add Data Source page and proceed to create the OAuth app in Wrike.

**Step 2 — Identify the Wrike administrator account**

Identify the Wrike administrator account you will use to create the OAuth 2.0 integration.

Required permissions: The OAuth 2.0 integration must be created by an Account Administrator.

**Step 3 — Create the OAuth 2.0 integration app in Wrike**

1. Open a browser and go to [login.wrike.com](https://login.wrike.com) and log in as the Account Administrator.
2. Navigate to the API Apps page:

* Click your profile icon in the upper-right corner and select Profile > Apps & Integrations.
* Select the API tab.

3. Enter an app name and click Create new. Wrike displays a configuration page for your new app, including the Client ID and Client Secret.
4. (Optional) Enter a description for the app.
5. Copy the Client ID and Client Secret and save them to a text file.

**Note**: Do not proceed until you have copied both values. You must provide them during onboarding.

6. Click Add Redirect URI and enter the redirect URL you copied from Cortex.
7. Click Save.

***

#### Task 2 — Connect SaaS Security to Wrike

1. Return to the Cortex onboarding flow (or navigate to **Settings > Data Sources and Integrations > Add New > Wrike tile**).
2. On the **Connections** tab, enter your Client ID, Client Secret, and Email ID.
3. Click Next. SaaS Security redirects you to the Wrike login page.
4. Log in to the Wrike administrator account. Wrike displays a consent form listing the access permissions SaaS Security requires.
5. Review the consent form and click Allow to grant the requested permissions.
6. On the Configurations tab:
   1. Set the Sync Interval.
   2. (Optional) Add a Tag.
7. Click Next to complete onboarding.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-xsiam/cloud-security/cortex-cloud-ai-security/cortex-cloud-saas-security/onboard-a-supported-saas-application/onboard-wrike.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.