Notion integration
Approved work lands in Notion, without copy-paste.
We write structured pages and database items into your Notion workspace with chunked, throttled writes.
How it works
The Notion API creates pages and database items, authenticated through an OAuth integration or an internal token. Notion has no draft, publish, or schedule concept in the API: a page simply exists once created. It also has real write limits, roughly three requests per second, 100 blocks per append call, and 1,000 blocks per page creation, so long articles are written in chunks with throttling handled by our pipeline.
Two things about visibility deserve plain words. First, an integration only sees pages and databases explicitly shared with it, and the API returns object_not_found otherwise, so our onboarding verifies the share step before anything else. Second, there is no API for Notion's Publish to web: content we write is public only if its parent already sits in a published Notion Site or feeds a front end you built. Notion is a destination workspace, and public visibility depends on what you have connected to it.
Best forTeams whose site or docs render from Notion, or who use Notion as the content home their front end reads.
Setup, step by step
- Create a Notion integration, or authorize SearchHandled through Notion's OAuth flow.
- Share the target page or database with the integration inside Notion, which is the step most setups miss.
- Add the connection in SearchHandled and pick the destination parent, a page or a database.
- For databases, map our fields to your database properties during setup.
- Run the connection check, which verifies the share and writes a small test page you can delete.
What lands in Notion
| Element | How it lands |
|---|---|
| Title and body | Converted to the native format, then verified by reading the entry back. |
| SEO metadata | Mapped to the platform's own fields, and flagged where it has none. |
| Images | Uploaded to your media storage with alt text. Never hotlinked. |
| Internal links | Rewritten to your live URLs and checked against redirects. |
| Publish state | Pages and database items. |
Field mapping is confirmed against your own content model during setup. Connectors are on every plan; the number of connected sites is what varies.
Best practices
Verify the share, then everything works
Nearly every Notion integration failure is a page that was never shared with the integration. Our onboarding checks it explicitly, and if you later move content to a new parent, share that one too.
Match database properties exactly
Pages created in a database must carry properties matching its schema. We detect the schema and map to it, so if your team renames or retypes a property, rerun the mapping.
Expect chunked writes on long posts
Notion caps blocks per request, so a long article arrives through several throttled append calls. A page may take a short while to fill in completely, which is the API working as designed.
Decide where public visibility comes from
Writing to Notion does not make content public. Know whether your public surface is a published Notion Site or a front end reading the API, and point us at the parent that feeds it.
Use it in the full SEO workflow
The connector is the last mile, not the strategy. Read the Notion SEO publishing workflow for the evidence gates, draft state, review rules, publish checks, and measurement loop that surround this integration.
Known issues
What practitioners actually report, from official docs, issue trackers, and community forums.
The integration must be shared with the target
API calls return object_not_found for pages and databases that exist but were never explicitly shared with the integration.
How we handle itOur onboarding verifies the share step against your chosen parent before the first real write, and our error messages name this cause specifically when it appears later.
developers.notion.com
No draft, publish, or schedule concept
The API cannot mark a page as draft or schedule it. A created page simply exists in the workspace immediately.
How we handle itWe hold content in our own review queue until approval and only then write to Notion, and for timed publishing we make the write itself at the scheduled moment.
developers.notion.com
Rate and block limits shape large writes
Writes run at roughly three requests per second, appends cap at 100 blocks, and page creation caps at 1,000 blocks, so naive bulk writes fail or get throttled.
How we handle itOur pipeline chunks block writes and throttles under the limit automatically, so long articles and batches land completely without rate-limit errors.
developers.notion.com
No API for Publish to web
There is no endpoint to make a page publicly visible. Content is public only if its parent already belongs to a published Notion Site.
How we handle itWe detect the parent type during setup and state plainly whether written content will be publicly visible, so nobody assumes a page went live when it landed in a private workspace.
community.latenode.com
Questions teams ask
- Can SearchHandled publish a page to the public web through Notion?
Not directly, because Notion has no API for Publish to web. Content becomes public when its parent is part of a published Notion Site or when your own front end renders it. We tell you which situation you are in during setup.
- Why did a write fail with object_not_found?
Almost always because the page or database was not shared with the integration, which Notion requires explicitly. Share the parent with the integration in Notion and the same write succeeds.
- How do drafts work if Notion has no draft state?
The draft lives in SearchHandled. Content stays in our review queue until you approve it, and only then do we write it to Notion, at the time you chose if you scheduled it.
Connect Notion
One tested path from approval to publish.
Bring your content model to setup. We will map the destination and validate a draft before anything goes live.