Skip to content
plugboard.appRequest a demo

Connectors

Wonde

Wonde connects a school’s student information system to the apps the school approves. The school approves Plugboard in Wonde, and Plugboard reads that one school’s students and staff through Wonde’s API. It never writes to Wonde.

CategoryStudent information
AuthenticationA Wonde school token that reads one school
Reacheshttps://api-ap-southeast-2.wonde.com
Needs an agentNo
Demo modeYes

Limited availability. We set this integration up with your team, starting with a pilot at your school, and check it with the provider before you rely on it. The connector is tested against Wonde’s published API reference, not against a school’s records.

sis.getRoster, sis.lookupStudent, sis.lookupStaff, sis.getTutorGroup, sis.getPhoto

Which lights up:

  • People: students on roll and current staff, with name, school email, username, card, year, roll class and campus, and each staff member’s start and end dates and role.
  • The roll class and its teacher, used by the ready-for-collection tutor email. Where Wonde lists more than one teacher on a roll class, Plugboard keeps the class and names no teacher rather than guess.
  • Staff photos, when the school approves Wonde’s photo permission and staff photos are on in Settings, Photos. Student photos are never read.

Lookups take a Wonde id only. Wonde offers no search by name, username or card, so names and cards come into Plugboard with the roster.

Plugboard never asks Wonde for medical, wellbeing, behaviour, attendance, assessment, family contact, salary, contract or employment-check records. It reads no student photos and never calls Wonde’s bulk photo list. Some replies carry more than Plugboard keeps, such as dates of birth, gender, phone numbers and addresses: those fields are dropped as each reply arrives, before anything is stored or logged. Raw replies are never kept, and Wonde’s own error text is never shown.

Every request is a read to Wonde’s Australian host, checked against a fixed list of the requests Plugboard makes before it leaves. Redirects are refused.

Plugboard uses four of the permissions a school can approve in Wonde: students.read, employees.read, groups.read and photos.read. Test connection and the start of every roster run read what the school approved:

  • Anything else approved is named in the test result, so the school can switch it off in Wonde.
  • Anything in the never group (medical, wellbeing, behaviour, extended details, regional data, salary, contracts, next of kin, employment checks) stops every run until the school switches it off. A token that can read medical records does not sit on a school’s server, even unused.
  • A school that withdraws its approval of Plugboard is treated as revoked access.

Each school has its own token, and it reads that school alone. A token that can read more than one school is refused. The token never travels by email and is never typed into the desk:

  1. The school approves Plugboard in Wonde, and Wonde issues that school’s token to Plugboard.
  2. Plugboard support pastes it into Plugboard’s own panel, where it is sealed at once.
  3. Someone at the school with connector.manage opens the Wonde connection’s row menu on Settings, Connectors, chooses Collect Wonde token, then Collect the token. The school’s server collects it once, over its licence key, straight into the connection’s sealed settings. Nobody sees it, and Plugboard keeps only a hash of the token and when it was collected.

Self-hosted schools collect the token the same way. Collecting a second time answers “No Wonde token is waiting for this school” until support stores a replacement.

Settings, Connectors, then Wonde under Add a service, and Continue to setup.

FieldValue
schoolIdThe school’s Wonde id, for example A1234567890
regionap-southeast-2, the only choice. Australian and New Zealand schools use it
maxRecordsThe most students and staff one pull may hold, from 100 to 100,000 (the default). A larger pull fails as a whole
demoModeReturn fictional people instead of calling Wonde

The token field stays empty. The token arrives through Collect Wonde token.

  1. Add the connection with the school’s Wonde id. Its first test fails, because it has no token, so choose Finish disabled.
  2. Collect the token, as above.
  3. Test the connection from its row. The test passes only when the token reads exactly one school, the configured one, and the school’s approved permissions include nothing from the never group. Then enable it with Review & enable.
  4. If the school’s people already came from another student system or a CSV import, choose Match people on the connection before the first sync. See the first sync of a student system.

On Plugboard’s demo, only demo mode works: Wonde reads real student records.

A pull applies nothing unless it is complete: every page read to the end, no repeated person, totals equal to Wonde’s own counts before and after, at least one student and one current staff member, and no more than maxRecords. Any other answer fails the whole run, and the next scheduled run tries again.

Wonde saysPlugboard does
The token is refused, or the school has withdrawn its approvalFails the run, raises a sticky alert for people with user.manage, deactivates nobody, and deletes the staff photos this connection supplied
The school is not foundFails the run. Check the school id
The school is inactiveFails the run. Nobody is deactivated, and the next run tries again
Too many requestsFails the run. Nothing is applied, and the next run tries again

The roster safety stops every student system shares apply too: the leaver cap per person type, the creation cap for a re-keyed roster, and Match people before the first sync. See people.

MessageCause
“Configure the Wonde school id and this school’s Wonde token.”The token has not been collected. Use Collect Wonde token
“No Wonde token is waiting for this school.”Support has not stored the token, or it was collected already. Ask Plugboard support
“This Wonde token can read more than one school (or none).”Wonde issued an app-wide token. Plugboard accepts only a token for one school
“This Wonde token belongs to a different school or region than the one configured.”The school id does not match the token. Check schoolId
“The school has granted Plugboard Wonde access to records it never reads”A never-group permission is approved. Ask the school to switch it off in Wonde
“Wonde refused the school token.”The school revoked access or the token was replaced. Ask support to store the current token, then collect it again
“Wonde’s totals changed or did not match what was read.”The roster changed during the pull. The next run tries again
“Wonde holds more records than the configured limit.”Raise maxRecords to cover the school
“Match people before the first sync” on PeoplePeople already came from another source. See People

Synergetic, Sentral, Compass Education and OneRoster read a student system directly. Each fills in the same person record, so the rest of the desk works the same whichever you run.