Before you start
This guide applies to builds that already show the Notion export panel. Open Library → Batch management → Notion in the extension workbench. Store review schedules and local test builds can differ; this guide does not mean every store release includes the feature. Export requires an active full-plan license.
Prepare a workspace you can administer and an ordinary blank page. Test one illustrated article before exporting a batch.
1. Create an internal connection
- Open the Notion developer portal and sign in.
- Create a connection, give it a name such as “My article archive”, and select the destination workspace.
- Choose Internal and save. Creating an internal connection requires workspace-owner access. If the workspace is missing, check your account and permissions.
2. Find and copy the Token
Open your connection, choose Configuration, and locate Internal Integration Secret. Reveal it and use its copy button. Labels may vary by Notion version or language; look for the connection’s API token or internal secret.
Paste the complete secret into the extension’s Connection Token field. Do not use the connection name, workspace name, page link or login password. Do not include labels, quotes, spaces or line breaks. Keep the secret out of chats, support screenshots and public pages.
3. Enable content capabilities
Enable and save these capabilities. Comment and user-information permissions are not needed for this export workflow.
- Read content: check the destination and inspect image blocks.
- Insert content: create article pages and upload resources.
- Update content: replace external image references with uploaded images.
4. Authorize a test page
- Create an ordinary page in the same workspace, such as “Article export test”. Start with a page, not a database.
- Open its top-right ••• → Add connections menu and add your new internal connection.
- Copy the full page link into the extension’s Destination page link or ID field. You do not need to extract the ID manually.
A Token alone does not grant access to the destination. The page does not need to be published on the web. Page access also extends to child pages, so use a dedicated archive page.
5. Test and export
- Click Test and save connection and allow the requested Notion API access in the browser.
- Select one illustrated article and click Export selected articles and images. Confirm that content will be sent to your Notion workspace. These button labels may appear in Chinese in the current extension.
- Keep the workbench open. When processing finishes, open the new child page in Notion and inspect the text, source link and images.
- Export the same article again to check that the existing page is skipped. Then select multiple articles for a batch test.
The connection test verifies read access. Write permissions are checked by the actual export. Content and images go directly from your browser to your Notion workspace. The Token is stored locally in the extension; this website never asks you to enter it.
Retries and duplicate protection
- Unfinished images: the article page may already exist. Failed images retain their external links. Retry unfinished items to continue without recreating the text.
- Additional image permissions: if prompted, allow the specific image origins and retry. File size, format and workspace limits can also cause failures.
- Existing pages: records are scoped to the connection Token, destination and local article. Existing pages are skipped even when local text changes, preserving your Notion edits. A new Token, cleared extension data or a different browser requires checking existing exports yourself.
- Unknown creation result: inspect the destination first. Only clear the protection for one article after confirming that no page was created.
- Closed workbench: processing stops. Reopen it and select the same articles and connection to continue. Do not delete existing pages merely because an export was interrupted.
Troubleshooting
“Please enter a valid Notion connection Token”
This is a local input check, triggered by an empty Token or whitespace, including line breaks. No connection request has been sent yet. Clear the field and copy the secret again using its copy button, without the surrounding label.
Invalid or revoked Token
Check whether the secret was copied completely, reset or revoked. Use the current secret for that connection.
Page cannot be accessed
Check that the connection and page belong to the same workspace, that the connection was added to the destination page, and that the copied link is correct.
Connection works, but export fails
Check Insert and Update content capabilities, an ordinary page destination, network access and workspace limits. Keep the per-article results and retry rather than repeatedly creating new connections.
The Notion panel is missing
Look under Library → Batch management, not the toolbar popup. If the installed release has no Notion panel, check future store updates; this guide does not add the feature to older builds.
Disconnect and references
Disconnecting in the extension removes the saved Token while retaining export-protection records and Notion pages. Revoke the connection or reset its secret in Notion to withdraw access there. This is a one-way export; Notion edits are not synced back to the local library.
See Notion authorization and connection capabilities. For help, use support and share only non-sensitive error details.