Skip to content
Storage ⇄ Business productivity

Box to Notion integration — real-time, two-way sync

Keep Box and Notion in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Box and Notion

Land the records and documents that build up in Notion into Box as they are created, and surface Box's file details on the Notion records that point to them, without an export job to maintain.

Notion and Box hold different kinds of data. Notion carries records and the activity around them — the tickets, messages, orders, or issues a team works through, often with documents attached. Box holds files and the metadata that describes them. Where the two meet is narrow but real: much of what Notion produces has to be kept somewhere durable, and many of the files Box stores are the very documents Notion's records point to.

Stacksync syncs Properties, Blocks, Formula and Rollup properties, Users in Notion with Tasks, Events, Files, Folders in Box in real time. Records and attachments created in Notion are written into Box as objects or files within seconds of being created. In the other direction, the metadata Box keeps about those files — name, location, owner, modified date — flows back onto the matching record in Notion, so people see the current document without leaving the tool. Field-level mapping controls exactly what crosses over and in which direction, so you keep a durable copy of what matters without an extract to schedule or a nightly dump that leaves the copy a day behind.

Common use cases

  • 01 Push rows from a warehouse or another database into a Notion data source as Pages so ops and leadership read live metrics in a familiar Notion view.
  • 02 Sync a Notion content-calendar database with Jira or Linear by mapping status and date properties both directions.
  • 03 Stream enterprise Events (admin events) into a warehouse for audit, DLP, and access-review reporting.
  • 04 Two-way sync of Files and Folders between Box and an operational database so applications track document status without calling the Box API directly.

Common sync patterns

Where Notion generates attachments: keep the files in Box

Documents attached to records in Notion land in the storage system automatically, with the source record holding a link back, so files live in one governed place instead of inside the tool.

Where Box holds the source documents: file details on the record

A file's name, location, owner, and modified date from Box sync onto the matching record in Notion, so whoever is working there sees the current version without switching tools.

A copy that outlives the tool

A continuously synced copy in Box preserves records and documents even as they age out of Notion or get changed inside it, so history stays intact and reachable.

What you can sync between Box and Notion

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Box objects Notion objects How this pairing syncs
Users Managed and app users in the enterprise; provisioned, updated, and deprovisioned to keep Box access aligned with an HR or identity source. Users Workspace members and bots referenced by people properties; read-only — users cannot be created or invited through the API. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Files Core content object with versions, name, size, and metadata; synced two-way so files and their attributes move between Box and a database or another store. Blocks The page body — paragraphs, headings, to-dos, tables — nested as children and fetched recursively, separate from a page's properties. Files is specific to Box and Blocks to Notion — each maps to any object or custom field on the other side.
Folders Hierarchical containers whose tree, names, and parent moves are mirrored so a target system reflects Box's structure; the account root is always folder ID 0. Formula and Rollup properties Values computed by Notion from other fields; read-only, so they are pulled out for reporting but never written back. Folders is specific to Box and Formula and Rollup properties to Notion — each maps to any object or custom field on the other side.
Metadata Structured key-value instances attached to files and folders via metadata templates; synced two-way with database columns for classification and search. Comments Page and inline discussion threads; can be read and created, useful for surfacing Notion activity in another system. Metadata is specific to Box and Comments to Notion — each maps to any object or custom field on the other side.
Collaborations Access grants linking a user or group to a file or folder with a role such as viewer, editor, or co-owner; written to manage sharing programmatically. Files and attachments File-property and file-block values. Notion-hosted URLs are temporary and expire, so files are re-fetched or copied at sync time. Collaborations is specific to Box and Files and attachments to Notion — each maps to any object or custom field on the other side.
Groups Named user collections used for bulk collaboration; membership synced from a directory or IdP. Pages The core content unit and also every row of a database; synced two-way as records, with typed properties mapping to table columns. Groups is specific to Box and Pages to Notion — each maps to any object or custom field on the other side.

How changes propagate between Box and Notion

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Box Notion Sub-second propagation

DetectionBox notifies Stacksync of record changes through webhook events. V2 webhooks fire on triggers such as FILE.UPLOADED, FILE.TRASHED, and METADATA_INSTANCE.UPDATED.

DeliveryEach detected change is written to Notion through its API, with automatic retries and rate-limit backoff.

Notion Box Sub-second propagation

DetectionNotion notifies Stacksync of record changes through webhook events. Workspace webhooks (page.created, page.content_updated, data_source.schema_updated, comment.created.

DeliveryEach detected change is written to Box through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Box: Per user: 1,000 API calls per minute and 240 file uploads per minute; exceeding limits returns HTTP 429 with a Retry-After header. Box Business plans also carry a licensed monthly API-call allotment per enterprise.
  • Notion: Average of ~3 requests/second per integration with some bursts; 429 with a Retry-After header when exceeded. Payloads capped at 500 KB and 1000 block elements.
What ships with Box ⇄ Notion

Connect Box and Notion for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Box–Notion connection.

Real-time

Two-way sync

Changes in Box or Notion instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Box or Notion data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Box or Notion record.

Observability

Monitoring

Track your Box ⇄ Notion sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Box and Notion.

How the Box and Notion connectors work

Box

Integration surface
REST API (api.box.com/2.0), plus the Events API and V2 Webhooks
Authentication
OAuth 2.0 for user-delegated access, or server-to-server auth via JWT (RSA keypair) or Client Credentials Grant (CCG) using a Box app; short-lived developer tokens for testing
Change detection
V2 webhooks fire on triggers such as FILE.UPLOADED, FILE.TRASHED, and METADATA_INSTANCE.UPDATED; the Events API (user stream via long-poll by stream_position, or enterprise/admin events) provides a near-real-time change feed
Capabilities
read · write · webhooks
Rate limits
Per user: 1,000 API calls per minute and 240 file uploads per minute; exceeding limits returns HTTP 429 with a Retry-After header. Box Business plans also carry a licensed monthly API-call allotment per enterprise.

Notion

Integration surface
REST API (api.notion.com/v1)
Authentication
OAuth 2.0 for public integrations, or an internal integration secret (bearer token); every request must send a Notion-Version header
Change detection
Workspace webhooks (page.created, page.content_updated, data_source.schema_updated, comment.created; HMAC-SHA256 signed) plus polling on each page's last_edited_time
Capabilities
read · write · webhooks
Rate limits
Average of ~3 requests/second per integration with some bursts; 429 with a Retry-After header when exceeded. Payloads capped at 500 KB and 1000 block elements.
How it works

How to connect Box to Notion — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Box and Notion with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Box connected
    Notion connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Box and Notion objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Box ⇄ Notion
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Box Notion
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Box and Notion integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 502 integrations available for Box and Notion.

Popular · 7 of 502
All Box integrations All Notion integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own