4.5/5 (300+ reviews)

Connect the campus systems you already run.

Abstract wavy blue lines pattern on a black background.

Sync records into the app, send engagement back to Slate and your CRM, and keep Builder as the place your event team works.

Connect Services

Campus systems

Sync records in, send engagement back, and keep Builder as the place your event team actually works.

Sync the records you already keep

Student profiles, schedules, custom lists, and ticket tiers come in from Slate, Eventbrite, Cvent, and the rest of the stack. Builder stays the source of truth for the app.

Send engagement back to the CRM

Export who showed up, what they opened, and how they used the app into Salesforce, Slate, Marketo, or Mailchimp. The next yield cycle starts from proof, not a spreadsheet.

Run it from Builder

Pick the integration, sign in, choose what syncs. No extra vendor portal for your event team. Campus IT still gets the Open API when the built-in connector is not enough.

Built-in integrations

Slate first. Then the registration, CRM, and campaign tools campuses already use.

Slate

Name, group, college, and major land in the app. Attendance and engagement go back.

View integration
Eventbrite

Open-house and yield registrants land in Builder, grouped by ticket tier.

View integration
Cvent

Attendees and session schedules come across once. Orientation week stays in one system.

View integration
Stova

Attendees, sessions, and speakers come in together for campus-wide programs.

View integration
Zapier

A Google Sheet — or the rest of the campus stack — can feed a guide.

View integration
Marketo

Export who showed up and what they opened into the next yield campaign.

View integration
Mailchimp

Export the attendee list and send it from the email tool campus already uses.

View integration
Salesforce

Send attendance and in-app activity back to the CRM the team already lives in.

View integration
Expo Pass

Check-in and custom badges sit next to the campus app on event day.

View integration
Try it FreeSpeak With Us

"Guidebook’s Open API has helped us integrate our custom scheduling system into Guidebook’s Builder. The API is easy to understand and the documentation is excellent.

‍The customer service has also been top notch. Compared to a competitor’s API we attempted to use last year, Guidebook has been a dream to integrate our system with"

JAMIE RYTLEWSKI
ACADEMY OF INTERNATIONAL BUSINESS
DATA THAT STAYS IN SYNC

Your Slate records and in-app activity stay in sync.

Student records flow from Slate into the app. Engagement flows back. No double entry, no manual imports - both tools stay on the data you already trust.

How guidebook connects with slate
Actionable data

App activity feeds back into Slate for outreach.

Always Up to Date

A change in Slate shows in the app instantly.

Data You Can Trust

Encrypted and protected at every step of the flow.

No double entry

Update once. Both tools stay on the same records.

Get up and running in minutes.

Unlock new potential with strategic technology integrations

1
Select the integration

Pick from the connectors already in Builder — Slate, Eventbrite, Cvent, Stova, Zapier, and the rest of the campus stack.

2
Log in to the service

Authenticate with the account your event team already uses. No second vendor portal to learn.

3
Select what to sync

Choose the lists, sessions, and fields that should land in the app — then keep working in Builder.

Open API

Docs and working examples for campus IT to wire Guidebook to the system of record.

Documentation

Browse the developer docs. REST endpoints for sessions, lists, attendees, and more — generate a key in Builder and start from the official reference.
Examples

Working samples on GitHub — starting points for a campus SIS, custom scheduler, or the system of record IT already runs.
Eventbrite integration example iCal integration example Salesforce integration example Mailchimp integration example
Try it FreeSpeak with Us