Do I need a Notion API key?

No. Lapu AI uses Notion the same way you do — via the desktop or web app, signed into your existing session. There is no API key to manage, no internal integration to install in your workspace settings, and no OAuth scopes to grant.

Will Lapu AI hit Notion API rate limits?

No, because Lapu AI does not call the Notion API. Notion's API enforces an average of 3 requests per second per integration, returning HTTP 429 errors when exceeded (developers.notion.com/reference/request-limits). Lapu AI drives the Notion UI instead, so bulk operations are paced by UI response time rather than API quotas.

Does Lapu AI understand Notion property types?

Yes. Lapu AI handles common property types — title, rich text, number, select, multi-select, date, person, URL, email, phone, checkbox, status — and respects the type when writing. If a column expects a date and the source value is a string, the agent reformats it or asks for confirmation.

Will Lapu AI create duplicate Notion pages?

Lapu AI checks for existing pages before creating, using a key field you specify (title, email, slug). For ambiguous matches, the agent pauses and asks for your decision rather than guessing.

Can I undo what Lapu AI does in Notion?

Notion has its own undo and version history on every page. Combined with Lapu AI's audit trail of every action, you can trace what changed and revert in Notion if needed.

Does this work with Notion AI?

Yes. Lapu AI drives Notion's UI; if Notion AI is enabled in your workspace, you can have Lapu AI invoke it as part of a workflow (for example, ask Notion AI to summarize a long page that Lapu AI just created).

Is my Notion data sent to Lapu AI servers?

No. Notion data flows between your machine and Notion. Lapu AI sends only the relevant context the model needs for reasoning to AI model providers — never your full workspace as bulk storage.

When should I NOT use Lapu AI for Notion work?

Use the Notion API directly if you need to sync tens of thousands of rows headlessly on a server, run scheduled jobs without a user session, or build a multi-tenant integration for other people's workspaces. Lapu AI is built for your desktop workflows — interactive, permissioned, local-first — not for production server pipelines.

knowledge management

Automate Notion with Lapu AI

Notion is a workspace for notes, docs, and databases. Lapu AI automates Notion the same way you do — by driving the desktop or web app through permission-based browser control — so you can move between local files, terminal, and Notion in a single workflow without API keys, OAuth setup, or Zapier middleware.

Download freeFree · macOS & Windows · No credit card

1-click uninstall
Cancel anytime
Files never leave your computer

Top Notion workflows

1. Bulk-create pages from a local folder
You have a folder of meeting notes saved as Markdown files. Lapu AI reads each file, parses the front matter for tags and date, and creates a Notion page in a target database with the right property values plus the file content as page blocks.
```
"Read every .md file in ~/notes/2026-Q2/ and create a Notion page in the 'Meeting Notes' database with the file's title, the date from front matter as a Date property, tags as multi-select, and the body as page content."
```
Tools used: file:read, browser:control
2. Sync a CSV into a Notion database
Spreadsheet data needs to land in a Notion database with the correct field types. Lapu AI maps columns to Notion property types (text, number, select, date, URL), asks for permission on the first row to confirm the mapping, then inserts the remaining rows.
```
"Read /Users/me/clients.csv and add each row as a new entry in the 'Clients' Notion database, mapping CSV columns to Notion properties. Pause on row 1 so I can confirm the mapping."
```
Tools used: file:read, browser:control
3. Draft a weekly digest from local sources
You want a weekly digest in Notion summarizing files you worked on. Lapu AI inspects file modification times via shell, summarizes content, and posts a Notion page with linked references.
```
"Find every file I edited in ~/projects/ this week, summarize what changed, and create a Notion page titled 'Week of [date]' under the 'Weekly Digests' parent page."
```
Tools used: shell:exec, file:read, browser:control
4. Move PDFs into Notion as embedded pages
You receive PDF reports and want them in Notion with extracted text and an embed for visual reference.
```
"For each PDF in ~/reports/, extract the text, create a Notion page with the text content as blocks, and attach the original PDF as a file embed."
```
Tools used: file:read, doc:pdf, browser:control
5. Clean up duplicate database entries
Your CRM-like Notion database has duplicates. Lapu AI scans visible rows, identifies likely matches by a key field (email, URL, name), and asks before merging or archiving each pair.
```
"Open the 'Contacts' Notion database, find rows that appear to be duplicates by email, and merge them with my approval on each pair."
```
Tools used: browser:control
6. Sync meeting notes from Apple Notes into a Notion database every Friday
You take quick notes in Apple Notes during meetings and want them in a structured Notion database at the end of the week. Lapu AI extracts notes modified this week, parses each into title and body, and adds them as new pages with the date and source tag.
```
"Every Friday at 4pm, read my Apple Notes modified since Monday, and for each one create a row in the 'Meeting Notes' Notion database with title, date, body, and 'apple-notes' as the source tag."
```
Tools used: file:read, shell:exec, browser:control
7. Convert a Notion page into a local Markdown export
You want to move a Notion page or a database view into version control or a static-site repo. Lapu AI opens the page, copies content block by block, and writes a clean Markdown file to disk with front matter mapped from properties.
```
"Open the 'Public Docs' Notion database, export each page as a Markdown file into ~/site/docs/ with title, slug, and tags as YAML front matter."
```
Tools used: browser:control, file:write

How it works

1
Open Notion in the desktop or web app
Lapu AI navigates to your Notion workspace just like you would — using your existing logged-in session in the Notion desktop app or a browser tab. No API key, no integration installation, no OAuth flow.
2
Read your local source files
The agent reads files from your filesystem (CSV, Markdown, PDF, Apple Notes export, etc.) using local tools. Content stays on your machine until the agent writes it into Notion.
3
Distinguish page content from database properties
Notion separates structured database properties (Name, Status, Date, multi-select) from free-form page content blocks (paragraphs, headings, embeds). Lapu AI handles each correctly — setting property values via the property panel and writing body content as blocks inside the page.
4
Create or update Notion pages with permission
Each Notion action is shown to you for approval. You can pre-approve a class of actions for the session (e.g. 'create rows in this database'), or confirm one-by-one. Every action is recorded in the Lapu AI audit trail.
5
Pace requests to avoid Notion throttling
Because Lapu AI drives the UI rather than calling the Notion API directly, it does not hit the 3-request-per-second API rate limit. The agent still paces clicks and waits for UI confirmation between actions, which keeps long bulk operations stable.

Permissions required

file:read — to read your local Markdown, CSV, PDF, or other source files
browser:control — to navigate and interact with Notion in the desktop or web app, including the property panel and page blocks
shell:exec — optional, for batch file operations (e.g. find recently modified files, list a directory tree)
file:write — optional, for exporting Notion content back to your filesystem as Markdown or JSON

FAQ

Do I need a Notion API key?: No. Lapu AI uses Notion the same way you do — via the desktop or web app, signed into your existing session. There is no API key to manage, no internal integration to install in your workspace settings, and no OAuth scopes to grant.
Will Lapu AI hit Notion API rate limits?: No, because Lapu AI does not call the Notion API. Notion's API enforces an average of 3 requests per second per integration, returning HTTP 429 errors when exceeded (developers.notion.com/reference/request-limits). Lapu AI drives the Notion UI instead, so bulk operations are paced by UI response time rather than API quotas.
Does Lapu AI understand Notion property types?: Yes. Lapu AI handles common property types — title, rich text, number, select, multi-select, date, person, URL, email, phone, checkbox, status — and respects the type when writing. If a column expects a date and the source value is a string, the agent reformats it or asks for confirmation.
Will Lapu AI create duplicate Notion pages?: Lapu AI checks for existing pages before creating, using a key field you specify (title, email, slug). For ambiguous matches, the agent pauses and asks for your decision rather than guessing.
Can I undo what Lapu AI does in Notion?: Notion has its own undo and version history on every page. Combined with Lapu AI's audit trail of every action, you can trace what changed and revert in Notion if needed.
Does this work with Notion AI?: Yes. Lapu AI drives Notion's UI; if Notion AI is enabled in your workspace, you can have Lapu AI invoke it as part of a workflow (for example, ask Notion AI to summarize a long page that Lapu AI just created).
Is my Notion data sent to Lapu AI servers?: No. Notion data flows between your machine and Notion. Lapu AI sends only the relevant context the model needs for reasoning to AI model providers — never your full workspace as bulk storage.
When should I NOT use Lapu AI for Notion work?: Use the Notion API directly if you need to sync tens of thousands of rows headlessly on a server, run scheduled jobs without a user session, or build a multi-tenant integration for other people's workspaces. Lapu AI is built for your desktop workflows — interactive, permissioned, local-first — not for production server pipelines.