Reference · built on requestConnectorFiles, documents & spreadsheets

Notion

Pages, databases and data sources, blocks, and comments from Notion workspaces through the Notion API.

Request accessPricing ↗

About

Notion is a workspace of pages, with databases that hold one or more data sources of typed rows. Teams keep wikis, project trackers, meeting notes, and task lists in it. The Notion API reaches those objects as JSON, one bearer token per integration, and only for the pages and databases the integration has been added to.

Through Fibric, an operator queries a data source, reads the pages behind each row, and proposes a page, a property change, or a comment. Nothing is written until you approve. Then one write follows, with a receipt: what changed, why, and how to undo it.

This is a reference listing. It documents what Fibric would read from Notion and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Pages and their properties, for pages the connection has been added to and their children
  • Rows of a data source through POST /v1/data_sources/{data_source_id}/query, with filter and sorts
  • Block content of a page, paginated with start_cursor and a page_size of up to 100
  • Comments on pages and blocks, when the Read comments capability is granted
  • Webhook events page.created, page.properties_updated, page.content_updated, data_source.schema_updated, and comment.created
  • Users by name and, with the matching capability, email

Proposed actions

  • Target capability: propose a new page under a page, database, or data source parent through POST /v1/pages
  • Target capability: propose a property update on a page through PATCH /v1/pages/{page_id}
  • Target capability: propose appending up to 100 blocks to a page through PATCH /v1/blocks/{block_id}/children
  • Target capability: propose a comment on a page, a block, or an existing discussion through POST /v1/comments

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Meeting prep from the project page

    Before a review, the operator reads the project page and the tasks data source it links to, then proposes a brief as a new child page listing what changed since last time.

    With Meeting Prep

  • Chase actions recorded in a database

    The operator queries an actions data source for items past their due date, proposes a comment on each page naming the owner, and leaves a record of what it asked and when.

    With Action Follow-up

  • Spot the missing article

    When support questions repeat and no page in the wiki data source matches, the operator proposes a stub page holding the question and the answer agents gave. You approve before it exists.

    With Knowledge Gap

  • Weekly review that reads the tracker

    Every week the operator reads status properties across a data source and proposes a summary page with counts by status and the pages that changed.

    With Weekly Review

Requirements

  • A Notion workspace where an admin can create an internal integration or install a public one
  • The integration added to each page or database it should read; children inherit that access
  • Content capabilities (Read, Update, Insert) and comment capabilities selected on the integration
  • A public HTTPS endpoint and a completed verification_token step if you want webhook events
Authentication
A bearer token: an internal integration's token, or an OAuth access token for a public integration, sent with the Notion-Version header on every request.

Limits

  • 600 requests per minute on Business and Enterprise plans, 180 per minute on other plans; a 429 returns rate_limited with Retry-After
  • A data source query stops at 10,000 results and reports request_status as incomplete
  • Rich text fields hold 2,000 characters, one request holds up to 100 blocks, and a payload caps at 500KB
  • Aggregated webhook events such as page.content_updated arrive with a delay of under a minute; retries stop after 8 attempts

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Notion ↗

Questions and answers

What is the difference between a database and a data source?
Since the 2025-09-03 API version, a database is a container for one or more data sources. Properties and rows live on the data source. Queries go to POST /v1/data_sources/{data_source_id}/query, and permissions are set at the database level.
Does Notion send webhooks?
Yes. You create a subscription in the integration settings, complete a one-time verification_token step, and validate each delivery with the X-Notion-Signature HMAC-SHA256 header. Events cover pages, databases, data sources, and comments. Some events are aggregated and arrive with a short delay.
Can the integration see the whole workspace?
No. A connection sees only the pages and databases it has been added to, plus their children. Capabilities on the integration decide whether it can read, insert, or update content, read or insert comments, and see user emails.
Ask about Notion

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Notion through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy