Wrike
Connect Wrike to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Wrike to collect ticketing evidence with automated compliance tests, switched on per workspace.
| Category | Ticketing |
| Connect with | API token |
| What a connection produces | Automated compliance tests |
| Wrike's guide | developers.wrike.com |
Connect with an API token
-
In Wrike:
- Sign in to Wrike and open the App Console (https://www.wrike.com/appconsole.htm?#/api).
- Open your application in the App Console and click Get token.
- Enter your password when asked.
- Copy the permanent token; Wrike shows it only once.
Where to find the other values:
- Host (optional): The host in your browser's address bar when you use Wrike: www.wrike.com, app-eu.wrike.com or app-us2.wrike.com.
- Account ID (optional): Not shown in the documented UI steps; the API returns it as AccountId (8 characters, A-Z and 0-9) in user profiles. Leave blank unless you have several accounts.
Wrike shows the secret only once, so copy it before you leave the page.
Wrike's public documentation does not cover every step.
The docs do not describe how to create the App Console application itself, or whether a permanent token can be limited to the read-only scopes wsReadOnly and amReadOnlyUser; the Query Contacts method lists Default, wsReadOnly and wsReadWrite. A permanent token acts as the user who created it.
Source: developers.wrike.com, developers.wrike.com, checked 2026-10-07.
The permissions Safeguard needs:
wsReadOnly,amReadOnlyUser. -
On Compliance › Connectors, open Wrike, click Connect, choose API token and fill in:
Field What to enter Access token Required. Stored encrypted and never shown again. Host (optional) — Account ID (optional) — -
Click Connect with token.
Frameworks
Safeguard's automated tests read Wrike and map to the controls below. When a test passes, the result is evidence toward each control it maps to, in every framework listed. It is evidence toward a control, not proof that the control is met on its own.
| Framework | Evidence | Controls | Tests |
|---|---|---|---|
| SOC2 | Automated tests | CC6.2, CC6.3 | 3 |
| ISO/IEC 27001 | Automated tests | A.5.16, A.5.18, A.6.5, A.8.2 | 3 |
| HIPAA Security Rule | Automated tests | 164.308(a)(3), 164.308(a)(4) | 3 |
| PCI DSS | Automated tests | 7.2.2, 7.2.4, 8.2.5 | 3 |
| NIST CSF 2.0 | Automated tests | PR.AA-01, PR.AA-05 | 3 |
These tests are switched on per workspace by the Safeguard team.
Related
- Ticketing connectors
- Compliance connectors: how connecting works, card statuses and multiple accounts
- Connector setup reference: every connector in one table
- Frameworks and connectors: how connectors provide evidence for frameworks