Close
Connect Close to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Close to collect crm evidence with automated compliance tests, switched on per workspace.
| Category | CRM |
| Connect with | API token, MCP server |
| What a connection produces | Automated compliance tests |
| Close's guide | developer.close.com |
Connect with an API token
-
In Close:
- Sign in to Close.
- Go to Settings › Developer › API Keys and click + New API Key.
- Enter an informative name so you can tell which integration uses the key.
- Copy the key now and paste it into API key. Close will not display it again; only the key's ID is shown afterwards.
Where to find the other values:
- Organization ID (optional): Not documented on the fetched page; leave empty unless you have it.
- Access token (optional): Only applies to OAuth apps; leave empty when using an API key.
Close shows the secret only once, so copy it before you leave the page.
Close's public documentation does not cover every step.
Close API keys carry the creating user's permissions; the grant here is the Admin role, which the help page does not mention explicitly. Where the Organization ID appears in the UI was not found.
Source: help.close.com, checked 2026-10-07.
The permissions Safeguard needs:
Admin. -
On Compliance › Connectors, open Close, click Connect, choose API token and fill in:
Field What to enter API key Optional. Stored encrypted and never shown again. Organization ID (optional) — Or, instead: Access token (optional).
-
Click Connect with token.
Connect with the MCP server
Choose MCP server: the address https://mcp.close.com/mcp is filled in. Sign in to Close when asked. It lets Griffin AI search Close; the compliance evidence comes from the API token connection.
Frameworks
Safeguard's automated tests read Close 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
- CRM 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