Safeguard Docs
Compliance ConnectorsSetup by categoryCommunications Platforms

Intercom

Connect Intercom to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.

Connect Intercom to collect communications platforms evidence with automated compliance tests, switched on per workspace.

CategoryCommunications Platforms
Connect withAPI token, MCP server
What a connection producesAutomated compliance tests
Intercom's guidedevelopers.intercom.com

Connect with an API token

  1. In Intercom:

    1. Open the Intercom Developer Hub (app.intercom.io/a/apps/_/developer-hub/app-packages) and open your private app, or create one for Safeguard.
    2. Go to Configure › Authentication in the app. Your Access Token is shown there; copy it.

    Intercom's public documentation does not cover every step.

    Source: developers.intercom.com, checked 2026-10-07.

    The permissions Safeguard needs: Read admins.

  2. On Compliance › Connectors, open Intercom, click Connect, choose API token and fill in:

    FieldWhat to enter
    Access tokenRequired. Stored encrypted and never shown again.
    Region (optional)—
  3. Click Connect with token.

Connect with the MCP server

Choose MCP server: the address https://mcp.intercom.com/sse is filled in. Sign in to Intercom when asked. It lets Griffin AI search Intercom; the compliance evidence comes from the API token connection.

Frameworks

Safeguard's automated tests read Intercom 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.

FrameworkEvidenceControlsTests
SOC2Automated testsCC6.2, CC6.32
ISO/IEC 27001Automated testsA.5.16, A.5.18, A.6.52
HIPAA Security RuleAutomated tests164.308(a)(3), 164.308(a)(4)2
PCI DSSAutomated tests7.2.4, 8.2.52
NIST CSF 2.0Automated testsPR.AA-01, PR.AA-052

These tests are switched on per workspace by the Safeguard team.

On this page