How to Connect Your Notion Workspace
Publish AI-generated articles as rich Notion pages with metadata, keywords, and cover images.
Before You Start
- 1A BlogAmplify account (free to create)
- 2A Notion account with a workspace
- 3A Notion database prepared for articles (see Step 1 for recommended columns)
Step-by-Step Guide
Prepare your Notion database
Before connecting, create (or choose) a Notion database where articles will be published. We recommend adding these columns so BlogAmplify can map article data automatically:
| Column Name | Property Type | Purpose |
|---|---|---|
| Name | Title | Article title (required) |
| Meta Description | Text | SEO meta description |
| URL Slug | Text | URL-friendly slug |
| Keyword | Text | Primary SEO keyword |
| Author | Text | Author name |
Only the Title column is required (every Notion database has one by default). All other mappings are optional — BlogAmplify will skip any fields that aren't mapped.
Log in to BlogAmplify
Sign in to your BlogAmplify account. If this is your first time, you'll be guided through the onboarding wizard — the integration step is at the end (Step 5). If you've already completed onboarding, go to Settings → Integrations from the sidebar.
Select Notion as your platform
On the integration page, you'll see four platform options. Click the Notion card to select it, then click "Connect to Notion" to begin the authorization flow.

Authorize BlogAmplify in Notion
You'll be redirected to Notion's authorization page. The process has two screens:
- Review permissions — Notion will show what BlogAmplify can do (view, edit, and create content in pages you select). Click "Select pages" to continue.
- Select your database — Use the search box or browse to find your database (e.g. "Blog Posts"). Check the box next to it, then click "Allow access".


Select your database
After returning to BlogAmplify, you'll see a confirmation that Notion is connected along with a Publish to database dropdown. Select the database where articles should be published.

Map your database properties
After selecting a database, BlogAmplify will load its properties and show a mapping interface. For each article field, select the corresponding Notion column from the dropdown.
Only compatible property types are shown for each field. For example, "Title" can only map to a title-type column, and text fields like "Meta Description" can only map to text or rich text columns.
Click "Save Mapping" when done. Unmapped fields will simply be skipped during publishing.

Complete setup
Click "Complete Setup" to finish. BlogAmplify will create full Notion pages in your selected database with the article content, featured image as the cover, and all mapped metadata properties.
Troubleshooting
"No databases found" after connecting
This happens when no databases were shared during the authorization step. To fix:
- Go to Integrations in BlogAmplify and click Disconnect
- Reconnect to Notion
- On the Notion authorization page, use the search box to find and select your database before clicking "Allow access"
Alternatively, open the database in Notion, click the "..." menu → Connections → search for "BlogAmplify" and add it.
Property mapping shows "No compatible property available"
Your database doesn't have a column with the required property type. Open your database in Notion and add the missing column. For example, to map "Primary Keyword", add a Text column called "Keyword". Then return to BlogAmplify and re-select the database to refresh properties.
Articles are missing some content or appear truncated
The Notion API has a limit of 100 blocks per request. BlogAmplify automatically splits long articles into chunks and appends them sequentially. If content appears truncated, the article may have exceeded the API rate limit. Try re-publishing after a few minutes.
Featured image is not showing as the page cover
BlogAmplify sets the featured image as an external URL cover. If it doesn't appear, the image URL may not be publicly accessible. Verify the image loads in a browser. Notion caches external covers, so it may take a moment to appear.
"Notion error (400)" or "Notion error (403)" when publishing
Common causes:
- 403: The integration no longer has access to the database. Re-add it via the database's Connections menu.
- 400: A property mapping is incorrect (e.g. mapping to a column that was renamed or deleted). Re-select your database in BlogAmplify to refresh the mapping.
- Token expired: Disconnect and reconnect the Notion integration.

