Brightpearl to Neo4j integration — real-time, two-way sync

Yes. Stacksync provides a managed, real-time two-way integration between Brightpearl and Neo4j: authenticate both systems, choose the objects to sync (such as Brightpearl's Products and Sales orders), map fields visually, and changes propagate both ways in milliseconds — no code required.

Change detection on Brightpearl: Webhooks for object created/updated events, with resource search polling as a fallback. On Neo4j: Neo4j Change Data Capture on Enterprise and Aura streams graph changes; otherwise Cypher polling on timestamp properties. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.

On the Neo4j side: Databases, Users & Roles, Nodes, Relationships, plus custom fields where Neo4j exposes them. On the Brightpearl side: Products, Sales orders, Purchase orders, Contacts. Stacksync auto-detects both schemas and converts types between the two systems.

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 Brightpearl and Neo4j: Where Brightpearl is the HR system of record: people data for internal systems; Controlled write-back; Read ERP records with a query. Worker and org records stay current in Neo4j for provisioning, access, and reporting systems that read from the database.

Brightpearl: REST API, organized into services (order, product, contact, warehouse, accounting). Authentication: OAuth 2.0 (authorization code grant) for current apps; legacy private and public apps authenticate with app reference and account token headers. 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.