Real-time
Two-way sync
Changes in Box or Neo4j instantly reflect in both systems. No stale data, no manual imports.
Storage ⇄ Database
Box to Neo4j integration — real-time, two-way sync
Keep Box and Neo4j 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 Neo4j
Keep Neo4j and Box in step: a row in Neo4j for every file in Box, with names, paths, metadata, and status staying consistent in real time, in both directions.
A database holds structured records; a storage system holds the files those records depend on, such as contracts, images, exports, uploads, and documents. The two describe the same things from opposite sides: a row in Neo4j says a file exists and carries its name, location, and status, while Box holds the bytes. Linked only by a hand-kept path or a one-off script, the two drift the moment a file is renamed, moved, or deleted and the record still points at where it used to be.
Stacksync syncs Users & Roles, Nodes, Relationships, Properties in Neo4j with Collaborations, Users, Groups, Tasks in Box bi-directionally and in real time. File attributes, including name, path or object key, size, type, modified time, owner, and tags or custom properties, map field by field to columns on the matching row, and a change on either side shows up on the other within seconds. New files appear as rows, metadata edits travel in the direction you choose, and deletes stay consistent, with conflict rules you set in place of nightly reconciliation scripts.
Common use cases
- 01 Sync product catalog and order history into Neo4j to power recommendation queries.
- 02 Feed identity and access data into a graph for entitlement and blast-radius analysis.
- 03 Two-way sync of Files and Folders between Box and an operational database so applications track document status without calling the Box API directly.
- 04 Mirror Metadata template instances on Files into database columns so contracts and assets are searchable and reportable alongside other business data.
Common sync patterns
Records that point at documents
Where a record in Neo4j references a file in Box, such as a contract, an image, an export, or an upload, the reference, path, and status stay consistent as files are renamed, moved, or replaced, so stored links keep resolving.
A landing zone for incoming files
Files that arrive in a folder or bucket in Box become rows in Neo4j as they land, so a database-driven process can pick them up without polling the storage system's API.
Continuous archival to file storage
Rows from Neo4j are written out to Box as files on a schedule or as they change, giving a durable, low-cost copy for backup, compliance, or a data lake, without a custom export job to maintain.
What you can sync between Box and Neo4j
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 | Neo4j 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. | Nodes Entity records (customers, products, accounts) written from source systems as labeled nodes. | Users is specific to Box and Nodes to Neo4j — 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. | Relationships Typed, directed edges that carry the connections syncs exist to model. | Groups is specific to Box and Relationships to Neo4j — each maps to any object or custom field on the other side. | |
| Tasks Review or approval assignments on a file with due dates and states; read for workflow reporting or written to start approvals. | Properties Key-value attributes on both nodes and relationships, mapped from source fields. | Tasks is specific to Box and Properties to Neo4j — each maps to any object or custom field on the other side. | |
| Events Enterprise admin event stream, an audit log of uploads, deletes, logins, and shares across the account; read-only, consumed for reporting or change feeds. | Labels Node type markers used to map source tables or objects onto the graph. | Events is specific to Box and Labels to Neo4j — each maps to any object or custom field on the other side. | |
| 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. | Indexes & Constraints Uniqueness constraints and indexes that make MERGE-based upserts reliable and fast. | Files is specific to Box and Indexes & Constraints to Neo4j — 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. | Databases Named databases in a single instance that scope multi-tenant or multi-domain syncs. | Folders is specific to Box and Databases to Neo4j — each maps to any object or custom field on the other side. |
How changes propagate between Box and Neo4j
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 Neo4j 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 Neo4j through its API, with automatic retries and rate-limit backoff.
Neo4j Box Sub-second propagation
DetectionChanges in Neo4j are captured at the source via change data capture — no polling loop against its API. Neo4j Change Data Capture on Enterprise and Aura streams graph changes.
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.
What ships with Box ⇄ Neo4j
Connect Box and Neo4j for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Box–Neo4j connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Box or Neo4j 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 Neo4j record.
Observability
Monitoring
Track your Box ⇄ Neo4j 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 Neo4j.
How the Box and Neo4j 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.
Neo4j
- Integration surface
- Bolt binary protocol with Cypher via official drivers, plus an HTTP query API
- Authentication
- Username/password (basic auth); enterprise deployments add SSO options
- Change detection
- Neo4j Change Data Capture on Enterprise and Aura streams graph changes; otherwise Cypher polling on timestamp properties
- Capabilities
- read · write · CDC
How it works
How to connect Box to Neo4j — 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.
- 01
Connect your apps
Authenticate Box and Neo4j with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Box
connected
Neo4j
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Box and Neo4j 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.
objects · Box ⇄ Neo4jCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Box Neo4jCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Box and Neo4j integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Box and Neo4j: authenticate both systems, choose the objects to sync (such as Box's Users and Groups), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
-
Common patterns for Box and Neo4j: Records that point at documents; A landing zone for incoming files; Continuous archival to file storage. Where a record in Neo4j references a file in Box, such as a contract, an image, an export, or an upload, the reference, path, and status stay consistent as files are renamed, moved, or replaced, so stored links keep resolving.
-
Box: 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. Neo4j: Bolt binary protocol with Cypher via official drivers, plus an HTTP query API. Authentication: Username/password (basic auth); enterprise deployments add SSO options. Stacksync manages authentication, retries, and rate limits on both sides.
-
Neo4j: Schema is optional, but uniqueness constraints and indexes are the standard way to make keyed syncs deterministic. Box: Server-auth apps (JWT or CCG) act through a service account and only see content that account owns or is collaborated on, unless enterprise as-user or admin scopes are granted. Stacksync's field mapping accounts for these differences between Box and Neo4j without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Box and Neo4j records are not retained after a sync operation.
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.
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 508 integrations available for Box and Neo4j.
Popular · 7 of 508
-
Box ⇄ Google Cloud SQL -
Box ⇄ IBM AS/400 -
Box ⇄ IBM Informix -
Box ⇄ InfluxDB -
Neo4j ⇄ Egnyte -
Neo4j ⇄ Amazon S3 -
Neo4j ⇄ Sharepoint
No integrations match .
