Make
Connect Make to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Make 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 |
| Make's guide | developers.make.com |
Connect with an API token
-
In Make:
- Sign in to Make and click your avatar at the bottom-left corner of the page.
- Click Profile and open the API tab.
- Click Add token.
- In the Add token dialog, enter a Label (for example Safeguard) and under Scopes select only the read scopes Safeguard needs, including user:read (required to list users).
- Click Save, then copy the token right away.
Where to find the other values:
- Zone: The zone is in the address bar of your Make organization dashboard, for example https://eu1.make.com/ (eu1) or https://us1.make.com/ (us1).
Make shows the secret only once, so copy it before you leave the page.
Make's public documentation does not cover every step.
Once you leave the Profile section Make hides part of the token and it cannot be copied again. Listing users needs user:read. The docs do not say where the UI shows the Organization ID; the API's list-organizations response returns organizationId. Zone location is from the official API structure page's indexed text. The organizations:read scope was not confirmed on the fetched pages.
Source: developers.make.com, developers.make.com, developers.make.com, checked 2026-10-07.
The permissions Safeguard needs:
user:read,organizations:read. -
On Compliance › Connectors, open Make, click Connect, choose API token and fill in:
Field What to enter Organization ID Required. API token Required. Stored encrypted and never shown again. Zone Required. For example: eu1 -
Click Connect with token.
Frameworks
Safeguard's automated tests read Make 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.1, CC6.2, CC6.3 | 4 |
| ISO/IEC 27001 | Automated tests | A.5.16, A.5.18, A.6.5, A.8.2, A.8.5 | 4 |
| HIPAA Security Rule | Automated tests | 164.308(a)(3), 164.308(a)(4), 164.312(d) | 4 |
| PCI DSS | Automated tests | 7.2.2, 7.2.4, 8.2.5, 8.4.2 | 4 |
| NIST CSF 2.0 | Automated tests | PR.AA-01, PR.AA-03, PR.AA-05 | 4 |
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