The third-party services Nexpura connects to — e-commerce (Shopify, WooCommerce), email marketing (Mailchimp), accounting (Xero), calendar (Google), messaging (WhatsApp via Twilio) — and the data-movement layer that ships alongside (CSV exports across every tenant table, plus the stable-but-undocumented public API). Eight pages: how each integration connects, what syncs in which direction, and the honest disclosure for the two pages where the current state differs from the intended state.
The integrations data model, how a connection is established and persisted, where in the product each integration is configured, and the role of the cron-runner layer that fires scheduled sync jobs.
Two-way sync of products, customers, and orders between Nexpura and Shopify. OAuth connection from the website builder, the sync directions on the integrations panel, and what gets reconciled by the daily background job.
REST API credentials connection for WordPress / WooCommerce stores. Product, customer, and order sync; webhook setup; the reconciliation behaviour that brings the two ledgers back into agreement.
Connect your Mailchimp audience by API key. Customers with marketing consent flow to your Mailchimp audience on demand or on a sync schedule. Setup, sync, and the consent-gating that keeps the export honest.
OAuth connection to your Xero organisation. Invoices created in Nexpura flow to Xero as draft invoices; the access token refreshes automatically. Setup, sync, and the per-tenant Xero organisation binding.
OAuth connection to your Google Calendar. Appointments and repair due dates appear as calendar events; manual sync, automatic sync, and the disconnect flow that revokes the token cleanly.
WhatsApp messaging via Twilio for customer notifications (repair-ready, bespoke-ready) and employee task assignment. Mechanically shipped end-to-end. The customer-facing channel routing is in a meaningfully partial state vs intended product design — what works, what doesn't, and how to manage the gap until SMS routing ships.
CSV exports across every tenant table for GDPR portability and backup. The public API endpoints exposed under /api are stable but don't yet ship with formal reference documentation — what's there today and how to work with it.