Notion Integration
Connect a Notion workspace to Cremit Argus using an internal integration token. Scan pages, databases, and code blocks for exposed credentials.
About this guide
This comprehensive guide will walk you through the complete setup process. Expected completion time: 5-10 minutes.
Overview
Argus's Notion integration scans workspace pages, databases, and code blocks for pasted API keys, tokens, and credentials. Uses a Notion internal integration token, so no OAuth flow is needed.
Prerequisites
- Notion workspace Admin or Owner
- Ability to create an internal integration in Notion
- A Cremit Argus account
Step-by-Step Setup
Step 1: Create a Notion internal integration
- Go to Notion > Settings > Connections > Develop or manage integrations
- Click New integration, name it 'Cremit Argus', and associate it with the target workspace
- Under Capabilities, enable Read content; leave Read user information optional
- Save and copy the Internal Integration Secret
Step 2: Share target pages with the integration
Notion requires each page or database to be explicitly shared with the integration.
- Open a top-level page (or the workspace root you want Argus to cover)
- Click the three-dot menu > Add connections
- Select Cremit Argus from the list
- Accept the propagation prompt so all nested pages inherit the connection
Step 3: Add Notion as a Scan Source in Argus
- Argus > Configuration > Scan Sources > New
- Select Notion as the source type
- Paste the Internal Integration Secret from Step 1
- Click Test Connection, then Create
Step 4: Select pages and databases to scan
Argus only lists pages that the integration has been invited to.
- Pages appear hierarchically; select the roots you want covered
- Databases are listed separately; enable the ones that store config or credentials
- Pages added later under a covered root inherit the scan automatically
Verification
To confirm the integration is configured correctly:
- The Scan Source shows Connected with a valid workspace name
- Shared page counts visible on the source page match what you see in Notion
- Editing a covered page triggers a re-scan within minutes
- No 'object_not_found' or 'unauthorized' errors in the activity log
Troubleshooting
Issue: Argus shows 0 pages even though the token is valid.
- Solution: You have not shared any pages with the integration. Notion does not auto-grant access; each root page must be explicitly connected.
Issue: A new sub-page was added but Argus is not scanning it.
- Solution: The sub-page's parent must have the integration connected with propagation accepted. Re-connect at the root level and confirm 'Add to all child pages'.
Key Benefits
- Covers a fast-growing documentation surface for modern teams
- No OAuth or service account juggling; a single workspace-scoped token
- Respects Notion's share-to-integration model; Argus sees only what you grant
- Code blocks, toggle blocks, and database fields are all scanned