The Notion connector allows Simpplr Enterprise Search to index your Notion content, making it easily discoverable and searchable directly within Simpplr.
With this connector, you can:
Bring Notion content into Simpplr Enterprise Search so users can find files alongside intranet content in one place.
Use advanced features like autocomplete, hybrid ranking, and Smart Answers on top of Notion content.
Indexed content from Simpplr Enterprise Search is available in:
In main search listing
Smart answers
Content types | Pages |
Metadata | Name, URL, Owner Details, Updated By Details, Created Time, Updated Time, Parent Reference, Object Type, Extension, Size, MIME Type, Permissions |
Permissions | Permissions are configured in Notion when the connector API key is created for the integration. Notion API does not expose access level information, the integration should be granted access only to the specific pages that are intended to be public or required for the connector. Additional layer of access control can be configured via the Audience filter. |
Indexing | Initial full crawl when the connector is created, followed by a full crawl every 6 hours. |
Multiple instances support | Multiple Notion connections can be configured in the Simpplr environment. |
Search features |
|
Objects and content supported
Objects - List the object types that are indexed, for example:
Pages
Metadata - For each indexed item, Notion captures:
Title
URL / link
Owner / collaborators
Created time and last modified time
Path / location (e.g.,page )
File type and size
Permissions model - Due to the lack of a publicly available API to fetch permissions, Permissions cannot be retrieved or read directly from Notion.
Versions and editions supported
Supported Notion editions: N/A
Not supported: N/A
Any minimum version or API requirement: N/A
Prerequisites
Before you begin, ensure the following:
Source system permissions
Notion Admin Access
Application / service account
Ability to create a Notion Api Key
Notion Documentation : Introduction - Notion Docs
Authentication and security
Authentication mechanism
Describe how Simpplr Enterprise Search connects to Notion L
Auth type: Api Key
Scopes or permissions required (examples):
Read Content
Read User Information Including user
Data security
Data storage and residency: Indexed content and ACLs from Notion are stored within your Simpplr Enterprise Search environment, in the same region as your Simpplr tenant.
Encryption in transit: Server-side encryption with Amazon S3 managed keys (SSE-S3), TLS encryption in Kafka.
Encryption at rest: SSL (TLS 1.2 or higher), Auth: OAuth 2.0 client-credentials.
Permission enforcement: Due to the lack of a publicly available API to fetch permissions, Permissions cannot be retrieved or read directly from Notion.
Create a new integration here : https://www.notion.so/profile/integrations/internal
Select the New integration button. Name the integration “Simpplr Enterprise Search”
Associate the integration with your workspace by selecting it from the drop down menu. (You can only do this if you are an admin of that workspace.) Select Submit.
Required Capabilities for Simpplr Enterprise Search - Notion Connector:
Read Content
Read
Pick the Integration Secret , copy and select Save
Provide the Integration with the content access from the configuration Page by selection the list of pages or Teamspaces from the dropdown
In Simpplr, go to: Manage Features → Enterprise Search → Add Source.
Search and Select “Notion”.
Enter basic information:
Connection Name: Simpplr Notion
Provide authentication details and select the certificate toggle in authentication method (Copied from the client Application):
Api Key
Click “Save” and “confirm”.
Configure Audience based filtering.
Include audiences
Exclude audiences
Monitor the initial full sync status (starts automatically) in the connector dashboard.
How the connector works over time:
Initial full crawl
All the content present in the Notion is indexed during the first run
How long it may take: Depends on the size of the content.
Deletion changes
Deleted items are removed from index at next sync.
Expected latency
With the default schedule (full sync every 6 hours), changes made to Notion content are generally reflected in Simpplr search results within 6 hours of the update, and the permission lag in the system can be up-to 6hours. (as the full Sync runs every 6 hours).
Default field mapping
Source field Notion → Index field Simpplr
Source field Notion | Index field Simpplr |
|---|---|
title | title |
URL | url |
Created (date/time) | created_time |
Last modified | last_edited_time |
Created by | created_by |
Last edited by | last_edited_by (same enrichment) |
Document ID | _id |
Body / plain text | body_content |
Parent / hierarchy | parent |
File name (attachments) | name |
File type | extension (leading dot, e.g. .pdf) |
Size (attachments) | size |
Search experience - how content from this connector appears in search:
Result layout: (Icon, Connector name, Folder name, title (name) as link, body(excerpt), Created Date, File Type icon, file type)
Available filters and facets:
Sources = Notion
File type
Owner
Created Date
Participation in advanced features:
Smart Answers / Q&A: Yes
Autocomplete: Yes
Recommendations / “Suggested for you”: N/A
Trending / popular results: N/A
Semantic / hybrid ranking: Yes
Maximum file size indexed | Files and attachments are not indexed. |
Permissions | Permissions are configured within Notion at the time of the connector API key creation for the integration. The Notion API does not expose access level information; therefore, the integration should be granted access exclusively to the specific pages designated as public or required for the connector's functionality. |
Unsupported file types | Compressed files are not supported, e.g., an archive file containing a set of PDFs (The file content is not searchable, however, the users can still search via file title.) |
Rate limits | N/A |
Preview limitations | No preview available for excel, or media files. |
Connector health and monitoring - Describe where admins can see status information:
Enterprise Search → Connector name
Available metrics:
Last sync status (Success / Warning / Failed)
Last sync time
Next scheduled sync
Sync Type
Total items indexed count
Common issues and resolutions. Example pattern:
Issue: Authentication failed, Failed to fetch the access token (invalid credentials or missing scopes)
Possible causes:
Incorrect API key
Permission for a given page is not Configured in Notion admin panel
Resolution:
Verify and re-enter credentials
Confirm required permissions are granted
When to contact support.
Authentication error persists even after trying the above-mentioned resolutions
Sync is stuck in the Pending state,
Sync is in progress but no documents are getting ingested.
Sync failure with cancelled error (when not cancelled manually)
Incomplete or Partial sync.
When contacting Support, include:
Connector name and instance ID (if available)
Organization URL
Approximate time and date of the issue
Error messages or screenshots
Steps you already tried
Q1. Can I connect multiple tenants or domains?
A. Multiple Notion connections can be configured in the Simpplr environment.
Q2. How often does Notion sync data?
A. The connector runs a full crawl on first setup and then there is Incremental sync with full scan run every 6 hours.
Q3. Are comments, revisions, or version history indexed?
A. Comments and individual versions are not indexed as separate items. The connector indexes the latest file metadata, including the last updated time and updated-by user.
Q4. What happens when a user loses access to an item in Notion Storage ?
A. The updated access permissions will be indexed during the next sync.
Note: Files are synced every 6 hours. However, the actual update time may vary depending on the volume of data created within that period. Under normal conditions, changes are reflected within 6-7 hours, provided there has not been a significant spike in data uploads.
Q5. Can I exclude certain sites/teams/folders from being indexed?
A. Documents can be included and excluded based on the permissions you configure in the Notion while creating the API key , you have the option to not enable this integration for any of the page , database
Q6. How are deletions handled?
A. Objects deleted from the source are permanently deleted from the index.