Guidebook + Slate: Connect event attendance to every student record

Recorded live on 10 November 2026. Guidebook's Slate integration closes the loop between student records and what actually happens at your campus events. Registration and event data flow from Slate into Guidebook, and attendance flows back to the student's Slate record, so your team can connect who registered with who showed up and what they engaged with.

This session walks through how the integration works, what's involved in setup, and answers to the questions Slate users asked live.

What syncs, and in which direction

  • Person data and event and session data come from Slate into Guidebook.
  • Attendance data and optional app usage data go from Guidebook back to Slate.
  • Registration syncs one way only, from Slate to Guidebook. This was a deliberate choice, made after customer calls, to keep Slate as the source of truth.
  • Check-ins through any Guidebook check-in method sync back to Slate as attended.
  • A newly launched feature sends each guide's QR code to Slate for use in your own communications.

How setup works

  • Every feature is modular, so you connect only what you need. Person records are the foundation and must be set up first.
  • The integration is API-based, with one web service per feature per Slate instance. Multiple instances are supported, such as prospective and enrolled students kept separately, and all of them are managed in Builder.
  • Pre-built suitcases and a Builder wizard handle configuration, and you can change it at any time.
  • Syncs run automatically on a cadence, roughly every one to two hours. Session changes made in Slate reach the app even after students have registered.
  • Documentation for every feature lives at guidebook.com/slate, and the team is reachable at slate@guidebook.com.

From the live Q&A

  • The integration is included in the Guidebook subscription, with no added cost or contracting. Connecting extra Slate instances doesn't require extra licenses.
  • App usage data is optional, and you can limit it to specific guides.
  • Events map as Slate folders and sessions as subfolders.
  • Additional person fields beyond the default suitcase can be sent and shown in the app.
  • Guests such as parents can use the guide but aren't synced to Slate. Only Guidebook users linked to a Slate record are. Builder's attendance export captures everyone.
  • Custom groups can't drive preset schedules through the integration yet. The current workaround is to build the group and preset in Builder.

The integration was shaped by calls with Slate users, and that feedback loop continues: requests raised in this session are going to the product team.

Get our Event Planning Checklist

Pre-event prep, day-of setup, and post-event follow-up all in one place..

By clicking Sign Up you're confirming that you agree with our Terms and Conditions.
Thank you for signing up!
Click here to download
Oops! Something went wrong while submitting the form.