Is the Notion integration live?

Not yet. RecordX puts the summary and action items in the web app for every meeting; you copy them into Notion. The planned integration writes to a Notion database you nominate via the official Notion API.

Both patterns are planned. A database entry per meeting is the primary flow - one row with columns for title, date, participants, summary and a link to the RecordX meeting. A per-project page appended with new meeting blocks is the alternative.

Which Notion plan is needed?

Notion's public API works on every plan including Free. The RecordX-created pages count against your workspace's normal page quota.

Will the full transcript go into Notion?

You'll choose per-workspace whether the body contains the summary only (recommended) or the full transcript. Very long transcripts hit Notion's 100-block-per-request write limit; RecordX will chunk automatically.

What's the workaround today?

Copy the summary or action-item block from RecordX and paste into a Notion page or database row. Or use the Notion Zapier / Make connector plus the RecordX action-item webhook.

RecordX + Notion

Category: docs / notes - Status: planned

Start for free → No credit card required.

What it does today

The Notion sync isn't shipped yet. Every RecordX meeting produces a summary, action-item list and full transcript in RecordX; you copy the pieces you want into Notion. The planned integration will use the official Notion API to write a database row per meeting (title, date, participants, summary, RecordX link) into a database you nominate, or append blocks to a project page.

Setup (once the sync ships)

Create your RecordX account at recordx.io/register.html.
Install the RecordX Chrome extension.
Open settings in the RecordX web app and click Connect Notion.
Approve the RecordX integration and pick the pages / databases to share with it.
Pick a default meeting-notes database (or destination page).
Map RecordX fields to database properties: title, date, participants, tags, meeting link.
Record a test meeting; check the row appears with the right properties filled.

Data sync (planned)

Data	Direction	Notes
Meeting title	RecordX → Notion	Title property of the new row.
Date	RecordX → Notion	Date property, matched to the meeting start time.
Participants	RecordX → Notion	Multi-select or Person property, if participants are Notion members.
Summary	RecordX → Notion	Rich-text block in the page body.
Action items	RecordX → Notion	To-do blocks in the page body; can also fan out to a separate tasks database.
Transcript	RecordX → Notion	Optional - off by default because full transcripts are long.
RecordX link	RecordX → Notion	URL property pointing at the source meeting.
Comments	Not synced	Notion comments stay in Notion; RecordX comments stay in RecordX.

Permissions and scopes

Notion's OAuth flow is page-scoped, not workspace-scoped: you explicitly tick which pages and databases the RecordX integration can see. The planned integration asks for insert-content on the pages you nominate. It can't read pages you haven't shared, and it can't upgrade its own access without you going back to Notion settings.

Pricing and limits

RecordX doesn't charge extra for the Notion sync. The Notion API is available on every plan including Free. Notion rate-limits at roughly 3 requests per second per integration and 100 blocks per write; long transcripts are chunked automatically. Notion AI, database views, and templates work on RecordX-created rows the same as any other.

Common gotchas

Property types have to match: a Text property can't take a Date value. Use the RecordX mapping step.
Notion API doesn't support two-way sync - RecordX writes, it doesn't watch database edits.
Long transcripts hit the 100-blocks-per-request limit; RecordX will chunk, but very large files still take multiple round-trips.
Sharing settings on the database still apply - if you restrict the database to guests, they still won't see it in Notion.

Alternatives while you wait

Zapier or Make: RecordX action-item webhook → Notion "Create database row".
Notion's browser web clipper - open the RecordX meeting page and clip.
Manual copy from the RecordX summary block into a database row.
Google Drive for the transcript file, Asana for the action items.

FAQ

Is the Notion integration live?: Not yet. RecordX puts the summary and action items in the web app for every meeting; you copy them into Notion. The planned integration writes to a Notion database you nominate via the official Notion API.
Page or database?: Both patterns are planned. A database entry per meeting is the primary flow - one row with columns for title, date, participants, summary and a link to the RecordX meeting. A per-project page appended with new meeting blocks is the alternative.
Which Notion plan is needed?: Notion's public API works on every plan including Free. The RecordX-created pages count against your workspace's normal page quota.
Will the full transcript go into Notion?: You'll choose per-workspace whether the body contains the summary only (recommended) or the full transcript. Very long transcripts hit Notion's 100-block-per-request write limit; RecordX will chunk automatically.
What's the workaround today?: Copy the summary or action-item block from RecordX and paste into a Notion page or database row. Or use the Notion Zapier / Make connector plus the RecordX action-item webhook.

Setup checklist

RecordX account and Chrome extension installed.
Meeting recorded and summary visible in the web app.
Notion workspace ready; meeting-notes database created with title, date, participants, link columns.
Participants exist as Notion members if you want the Person property auto-filled.
Decide up front: summary-only vs summary + transcript.

Related integrations

Asana, ClickUp, Linear - dedicated task alternatives.
Google Drive, Dropbox - if the transcript file is the artifact you want.
Zapier - the fastest way to build a Notion pipe today.
See all integrations.

Start for free