Notion
LiveAPI KeyAutomation
Overview
Automatically add identified companies and hot leads as pages in your Notion databases. ClearView creates rich database entries with company details, lead scores, and engagement data. Use Notion's views, filters, sorts, and relations to build a powerful lead tracking system right inside your existing workspace.
What Gets Synced
- Database pages - Each company or hot lead creates a new page in your Notion database
- Rich properties - Company name, domain, industry, size, lead score, grade, and location
- Timeline data - First seen and last seen dates to track visitor engagement
Supported Events
| Event | Description |
|---|---|
company.identified | Fires when a new company is identified visiting your site |
lead.hot | Fires when a visitor is classified as a hot lead |
Prerequisites
- A Notion workspace with a database for receiving ClearView data
- A Notion Internal Integration token with read and write content permissions
- The database must be shared with the integration
- ClearView tracking script installed on your site
Setup Guide
Create a Notion integration
Go to notion.so/my-integrations and click "New integration". Give it a name like "ClearView" and select your workspace.
Set permissions
Under Capabilities, enable "Read content" and "Insert content". These permissions allow ClearView to create new pages in your databases.
Copy the integration token
Click "Show" next to Internal Integration Secret and copy the token (starts with secret_).
Keep your token secure
Share your database with the integration
Open the Notion database where you want ClearView to add records. Click the "..." menu in the top-right, select "Add connections", and choose your ClearView integration.
This step is required
Copy your database ID
Open the database in Notion. The database ID is in the URL: notion.so/your-workspace/DATABASE_ID?v=... Copy the 32-character ID (before the ?v= parameter).
Configure in ClearView
Go to ClearView Dashboard > Integrations > Notion. Enter your integration token (secret_xxx) and database ID. Select your events and save.
Test the connection
Click the Test button in ClearView. A new page should appear in your Notion database within a few seconds.
Configuration Fields
| Field | Type | Description |
|---|---|---|
apiKey | Secret | Internal Integration Secret (starts with secret_). Created at notion.so/my-integrations. |
databaseId | String | The 32-character Notion database ID. Found in the database URL before the ?v= parameter. |
Data Mapping
| ClearView Field | Notion Property | Property Type |
|---|---|---|
| Company Name | Name (Title) | title |
| Domain | Domain | url |
| Industry | Industry | select |
| Employee Count | Employees | number |
| Lead Score | Lead Score | number |
| Lead Grade | Grade | select |
| Source Page | Source | url |
| Country | Country | select |
| First Seen | First Seen | date |
| Last Seen | Last Seen | date |
Example Payload
ClearView creates pages using the Notion API. Here is the structure of a page creation request:
{ "parent": { "database_id": "your-database-id-here" }, "properties": { "Name": { "title": [ { "text": { "content": "Acme Corp" } } ] }, "Domain": { "url": "https://acme.com" }, "Industry": { "select": { "name": "Technology" } }, "Employees": { "number": 250 }, "Lead Score": { "number": 87 }, "Grade": { "select": { "name": "A" } }, "Source": { "url": "https://yoursite.com/pricing" }, "Country": { "select": { "name": "US" } }, "First Seen": { "date": { "start": "2026-03-20" } }, "Last Seen": { "date": { "start": "2026-03-25" } } }}Custom database properties
Troubleshooting
"Could not find database" error
Make sure the database is shared with your integration. Open the database in Notion, click the "..." menu, select "Add connections", and add your ClearView integration.
Property validation errors
Ensure your database properties match the expected types (title, url, select, number, date). If a property type is wrong, update it in Notion or adjust the column name to match.
Rate limit errors
The Notion API allows 3 requests per second. ClearView batches requests to stay within this limit, but very high-traffic sites may encounter occasional rate limiting. Events are automatically retried with exponential backoff.