# Wonde integration Wonde is an SIS data aggregator — rather than connecting PortalHQ directly to your SIS, you connect Wonde to the SIS, and PortalHQ connects to Wonde. This adds a layer but means PortalHQ can integrate with any SIS Wonde supports without building a custom connector. Used most commonly by schools running non-mainstream SIS systems, or by international schools where Wonde provides better SIS coverage. ## When to use Wonde Use Wonde if: - Your SIS isn't directly supported by PortalHQ (Edumate, Sentral, Synergetic, TASS, Compass, Edge are direct). - You're at an international school and Wonde has a connector for your SIS. - You already use Wonde for other integrations (e.g. payment systems, library systems) and want one consistent data source. If your SIS is directly supported, use the direct integration — it's lower latency and one less moving part. ## What PortalHQ reads via Wonde Wonde abstracts the SIS data into a common schema. PortalHQ reads: - **Students** — name, year level, gender, date of birth, photo. - **Parents / guardians** — name, email, phone. - **Staff** — name, email, role. - **Classes and lessons** — class lists, teachers. - **Timetables** — periods. - **Year groups and registration groups**. Some specific fields available in direct integrations (e.g. detailed medical alerts) may not be exposed through Wonde — depends on the underlying SIS and Wonde's connector. ## How the sync runs | Sync | Frequency | |---|---| | **Full sync** | Overnight (daily) | | **Delta sync** | Hourly | Write-back is **not currently supported** through Wonde — co-curricular enrolments and other write-back features that work with direct integrations don't flow back via Wonde. ## Setting up the integration 1. **Sign up for Wonde** and connect your SIS to Wonde — the Wonde team handles SIS-side setup. 2. **Authorise PortalHQ in Wonde** — Wonde issues an authorisation for PortalHQ to read your school's data. 3. **Share the Wonde school ID and access token with PortalHQ**. 4. **PortalHQ configures the connector** to point at the right Wonde endpoint. 5. **Test sync**, validate data, enable schedule. ## Wonde-specific notes - **Data latency** — Wonde caches SIS data. There's an additional latency layer between your SIS and PortalHQ — typically up to a few hours. - **Field coverage** — Wonde's common schema doesn't cover every SIS field. If a critical field is missing, check whether a direct integration is feasible. - **Cost** — Wonde charges schools a subscription fee. Factor this in vs. direct integration. ## Common issues | Issue | Likely cause | Fix | |---|---|---| | Sync stops at a partial state | Wonde quota exceeded | Check Wonde dashboard, contact Wonde support. | | Some fields missing | Field not exposed in Wonde's schema for your SIS | Confirm with Wonde whether the field can be added, or move to a direct integration. | | Stale data | Wonde cache lag | Wonde refreshes from the SIS on its own schedule; PortalHQ syncs from Wonde. Plan for some latency. | ## When to switch to direct If your SIS becomes one of the directly supported ones, switching from Wonde to direct integration is straightforward — most schools see better data freshness, fewer fields lost in translation, and lower cost. The migration plan involves mapping the Wonde-based external IDs to the direct SIS IDs.