Wonde sync — schools, staff and rooms from your MIS

Wonde sync

Wonde is a UK MIS aggregator — connect once to Wonde and Keystone can read schools, staff, and room directories from any of the major school MIS systems behind it (SIMS, Bromcom, Arbor, etc.). The sync is one-way: Wonde → Keystone. Keystone never writes back.

Connecting the integration

There’s no API token to enter — Alresford holds the Wonde commercial contract on your behalf, and the credential is provisioned in the licensing portal as part of your onboarding. In Admin → Integrations → Wonde you’ll see one of these statuses:

• Provided by Alresford — the credential is in place, you’re good to go. Toggle the switch to enable sync, pick a cadence, and save.
• Not yet provisioned — your trust is entitled to Wonde but no credential has been set up yet. Email support@keystoneops.education and we’ll wire it up.
• Wonde not included on your licence — Wonde MIS sync is an add-on. Email sales@keystoneops.education to enable it.
• Licensing portal unreachable — outbound network issue between your helpdesk and the Alresford licensing portal. The sync will retry automatically; if the banner persists, check egress firewall rules.

Once enabled, the form lets you choose the cadence (daily / weekly / manual) and toggle JIT enrichment on SSO. The default is daily at 01:00 trust-time.

What the sync does

Each scheduled run dispatches one job per entity type:

• Schools — pulls the school record itself: name, address, phase, URN. Maps to Keystone’s core_schools table.
• Staff — pulls every staff record with a contract (so historical leavers don’t pollute the directory). Creates or updates a Keystone user per staff member, tagged with their MIS staff code.
• Rooms — pulls the school’s room directory. Maps into Estates as Place records, scoped to the school.

A run is one row in the run log with start time, end time, status, and counts for created / updated / skipped / failed. The most recent run for each entity type is shown on the integration page. Failed runs surface their error message inline so you can decide whether to retry.

Reading the run log

The run log lives at the bottom of the integration page. Each row shows:

• When the run started and how long it took.
• Entity type (one of schools, staff, rooms).
• Outcome — completed, failed, or running.
• Counts — created, updated, skipped, failed.

A failed run does not stop the schedule — the next scheduled run will try again. If the failure is a Wonde-side authentication issue (token revoked, school disconnected) the integration will surface the error on the form so you can re-verify.

Manual runs

The Run now button on each entity row dispatches an immediate sync without waiting for the schedule. Useful after an MIS change-of-state (new staff intake, room renumbering) when you don’t want to wait for the next nightly run.