Workato
Connect Workato to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Workato to collect security automation evidence with automated compliance tests, switched on per workspace.
| Category | Security Automation |
| Connect with | API token |
| What a connection produces | Automated compliance tests |
| Workato's guide | docs.workato.com |
Connect with an API token
-
In Workato:
- Sign in to Workato and go to Workspace admin › API clients › Client roles, then select Add client role.
- Enter a name for the role and, under the workspace collaborators section, select only the Get collaborators (GET /api/members) endpoint. Click Save.
- Go to Workspace admin › API clients and select Create API client.
- Enter a name, select the client role you just made, select the environment if environments are shown (Workato says API clients require access to the DEV environment to manage collaborators), and select the projects it may access. Optionally add allowed IP ranges.
- Copy and store the API token, then click Save.
Where to find the other values:
- Data center: The Workato address you sign in to: www.workato.com (US), app.eu.workato.com (EU), app.jp.workato.com (JP), app.sg.workato.com (SG), app.au.workato.com (AU) or app.il.workato.com (IL).
Workato shows the secret only once, so copy it before you leave the page.
Workato says you will not be able to retrieve the API token again. The data-center-to-login-URL mapping is inferred from the documented API base URLs. The exact section heading under which Get collaborators appears in the client role editor was not quoted.
Source: docs.workato.com, docs.workato.com, docs.workato.com, checked 2026-10-07.
The permissions Safeguard needs:
Get collaborators. -
On Compliance › Connectors, open Workato, click Connect, choose API token and fill in:
Field What to enter API token Required. Stored encrypted and never shown again. Data center Required. -
Click Connect with token.
Frameworks
Safeguard's automated tests read Workato 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
- Security Automation 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