Running on Notion?

Notion API rate limited or workspace unwieldy? We sort it out.

Notion is a flexible doc, wiki and database tool, which means every workspace eventually becomes a collection of databases that nobody can explain. We clean up the database schemas, write the API integrations that actually survive rate limits, and migrate workspaces onto or off Notion without losing the content people rely on.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

notion-api.log

still broken

What it is

Notion at a glance

Notion is a collaborative document and database tool founded in 2013 by Ivan Zhao and Simon Last, and now used by tens of millions across companies, schools and personal setups. It mixes rich-text documents, databases with multiple views (table, board, calendar, gallery, timeline), simple formulas and a public API for building integrations.

The flexibility is Notion's strength and its weakness. A workspace that started as a scratchpad grows into dozens of interlinked databases with inconsistent schemas, rollups that break when a related property is renamed, and automations that only one person understands. The public API is capable but strict about rate limits (around three requests per second averaged), block structure and schema validation. Most integration problems we see are one of those three.

Type
Collaborative docs, wiki and database platform
First released
2016 current platform (company founded 2013)
License
Proprietary SaaS, per-seat pricing with Free, Plus, Business and Enterprise tiers
Maintained by
Notion Labs, Inc.
Typically used for
Internal wikis, project trackers, CRM lite, docs, lightweight databases, API-fed dashboards

The honest version

Notion pros and cons

No technology is all upside. This is where Notion earns its place and where it tends to cause trouble.

Where Notion is strong

  • Docs, wiki and databases in one toolA single workspace covers meeting notes, internal wiki, project tracker and a hundred ad-hoc lists, with the same editing surface for each.
  • Databases with multiple viewsThe same underlying data renders as a table, board, timeline, calendar or gallery, which often replaces three lightweight tools with one.
  • The public API is capablePages, databases, blocks, users and comments all have full CRUD coverage, so building a syncing dashboard or a CMS backed by Notion is genuinely possible.
  • Collaboration is smoothReal-time co-editing, comments, mentions, inline databases and share links behave the way users expect, with granular permissions when the account plan allows them.
  • Templates make bootstrap fastEntire workspaces, from a startup OS to a personal GTD setup, can be duplicated and tweaked, which cuts the cost of starting a new area.
  • SCIM and SAML for EnterpriseOn the Enterprise plan, provisioning and SSO are first-class, which makes Notion a defensible choice for organisations that need audit trails and lifecycle management.

Where Notion bites

  • Workspaces drift into chaosEvery team member can create pages and databases, and after a year the wiki has three home pages, two CRM databases and nobody is sure which is current.
  • Rate limits make serious integrations harderThe three-request-per-second average forces bulk operations to batch carefully, and a naive sync tool quickly hits 429s under real load.
  • Block limits are restrictiveAppends are capped at 100 blocks per request, pages have soft limits, and large documents become harder to edit the bigger they get.
  • Formulas and rollups are brittleA property rename, a deleted related row or a schema change can break rollups and formulas silently, with no good way to find every reference.
  • Offline and performance are weakThe desktop and mobile clients still struggle with large workspaces and poor connectivity. A field user with intermittent wifi gets a worse experience than the docs suggest.
  • Export is limitedWorkspace exports produce Markdown, HTML or PDF, but references between pages, database views and some block types do not survive cleanly, which makes a 'leave Notion' plan more work than it looks.

Sound familiar?

Common Notion problems we fix

The Notion problems that bring people to us, and what you have once each one is fixed.

429 rate_limited (3 req/sec)

An integration keeps hitting rate limits

A sync that fans out one API call per row without batching, or a backfill that treated the three-per-second average as a hard ceiling rather than a soft one to stay well under.

Sync inside the rate limit and durable

Rollup references deleted relation

Rollups show errors across a database

A related database that was renamed or merged, or a property that was deleted while rollups still referenced it. The database looks broken until each rollup is repointed.

Rollups green and reporting

body.filter.property is not defined

API queries fail validation

A filter referring to a property name that was renamed in the UI but still used in code, or a filter shape that was valid in an older API version and is strict in the current one.

Queries valid against the live schema

content exceeds 100 blocks per request

A bulk-write integration is failing

An importer pushing an entire doc as one append, or a template that expands to more than a hundred blocks in a single call. The fix is to chunk, not to hope it goes through once more.

Imports chunked and complete

Select option 'Blocked' not in schema

API writes are rejected for 'unknown' values

A status or select property that has to be defined in the schema before it can be written, which catches integrations that assume Notion will create the option on the fly.

Schemas aligned with the integration

object_not_found: database abc123

An integration lost access

An integration that was removed from a parent page, a database that was moved under a page the integration cannot see, or a shared workspace that revoked access during a cleanup.

Access restored and documented

Team plan page limit reached

A workspace has hit a plan limit

The Free and Plus tiers have page or block ceilings that are easy to hit in a growing company. The choice is either to upgrade or to archive a chunk of old content.

Plan matched to workspace size

What we do

Notion help, workspace to API

Bring us one broken rollup, or hand us the whole workspace to clean up.

Rescue
Integrations rate-limited, rollups broken, or a workspace that nobody can find anything in. We get the critical paths working and document the mess second.
Workspace audits
Every top-level page reviewed, duplicates merged, databases given consistent schemas, and the orphan corners archived rather than left to confuse new hires.
Notion API integrations
Sync tools that respect the rate limit, batching appends under the 100-block ceiling, filter queries validated against the live schema, and durable retries on transient 500s.
Migrations onto Notion
Moving content from Confluence, SharePoint, Google Docs or Dropbox Paper into a workspace whose structure is planned, with permissions that match the source.
Migrations off Notion
Exporting to Markdown, HTML or a target system, rebuilding cross-references, and keeping the team productive during the transition.
Managed Tech
Monthly workspace health checks, integration uptime, deprecation watch for API changes, and an engineer who can jump in when a critical database looks wrong.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Notion alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Notion questions

Something else? Call+1 737 727 7327

Why does our Notion API integration keep hitting 429?

The documented average is around three requests per second, and most integrations we see were written to push closer to that than a real production system should. The fix is to batch reads, cache page and database metadata, and use a token-bucket client that respects Retry-After. Once the integration lives under two requests per second comfortably, the 429s stop and the sync becomes boring.

How do we clean up a messy Notion workspace?

The honest answer is: an audit, not a redesign. We go through every top-level page, mark what is current and what is dead, merge the duplicate wiki homes, and give the surviving databases consistent schemas. The redesign happens later, on top of a workspace where you can at least find what is live.

Can Notion replace Confluence or SharePoint for us?

For a small to medium company, often yes. Notion is faster to use, cheaper per seat under Enterprise, and the editor is markedly better. For organisations with heavy compliance, deep SharePoint integration into Office workflows, or large document workflows, the move is possible but not trivial. We will give you the real comparison against your actual content.

How do we migrate from Notion to a target system?

Workspace export gives you Markdown, HTML or PDF, which covers most of the content but loses some references, views and block types. The real migration is rebuilding the cross-links, mapping database views to the new tool's model, and cutting over in phases rather than deleting the Notion workspace on day one. We plan the migration backwards from what the target system actually supports.

Why do our rollups and formulas keep breaking?

Because a renamed property, a deleted row or a schema change in a related database silently invalidates the rollup. Notion gives no good way to see every reference. The fix is to standardise the schemas across related databases, document the dependencies, and keep the number of rollups to the ones that actually drive a decision rather than a nice-to-have.

How much does Notion help cost?

We quote for free. Describe the workspace or the integration that is failing, and we come back with a scope and a fixed price before we open the share link.

Free estimate

Notion giving you trouble?

Workspaces, databases, rollups, API integrations and migrations in either direction. We work on the whole Notion surface.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.