Connect Google Calendar to Werp™ to write Werp™ bookings to Google Calendar and to import events from Google calendars linked to specific units as read-only bookings (up to 60 days ahead). Edits made in Google to events that came from Werp™ are not copied back.
Click Connect Google Account and complete the OAuth flow.
3
Load calendars
Click Load calendars to fetch your available Google Calendars.
4
Create a unit binding
Select a unit and a Google Calendar to link them.
5
Enable sync direction
Toggle Read from Google and/or Write to Google.
6
Initial sync
Click Sync now to do the initial import.
Read direction: Google Calendar → Werp™
Events from the linked Google Calendar are imported as bookings in Werp™ with sourceType: google_calendar. Events from today up to 60 days ahead are covered, and the import runs automatically every hour, and also when someone opens the booking list or the Kiosk, or presses Sync now (it is not continuous, so an event added in Google can take up to about an hour to appear). These bookings are read-only — they appear in all calendar views and on the Kiosk, and are treated as conflicts when new Werp™ bookings are created. They cannot be edited or deleted from within Werp™.
Write direction: Werp™ → Google Calendar
When "Write to Google" is enabled, Werp™ bookings you create are automatically added to the linked Google Calendar. The event description includes the borrower name, equipment details, and a link back to Werp™. Editing or deleting a Werp™ booking also updates the Google Calendar event.
One-way sync limitation
If you edit a Werp™-originated event directly in Google Calendar, those changes are not reflected back in Werp™. Always make changes in Werp™ to keep data consistent. Google Calendar-side conflicts (e.g., two events overlapping from different calendars) are not automatically resolved.
Auto-sync on Kiosk
While the Kiosk page is open, Werp™ checks whether the linked calendar has been synced within the last 5 minutes. If not, it syncs in the background, so the day timeline is at most about 5 minutes behind.
Use case scenarios
Video production team
Camera bookings appear in the team's shared Google Calendar automatically. The director sees "Axeon M7 IV: Alex, Thu–Fri" alongside crew calls and location scouts — without ever opening Werp™.
Conference room management
A conference room projector is linked to the room's Google Calendar. When someone books "Board Meeting, 14:00–16:00" in Google Calendar, Werp™ imports it as a conflict. Anyone trying to book the projector during that slot is blocked — even if they never looked at Google Calendar.
Zero-friction team adoption
Most team members don't change their workflow at all. Equipment bookings appear in the calendar they already check every morning. They see "Projector: Maria, Wednesday" and know the projector is taken — no chat message needed, no Werp™ account required to see it.
Kiosk: Google Calendar bookings cannot be extended or ended
When a Google Calendar event is the currently active booking on the Kiosk, the Extend and End Now buttons do not appear. Modifying those bookings from the Kiosk is intentionally blocked — changes made to Google Calendar events in Werp™ would be silently overwritten on the next sync. To extend or end a Google Calendar-sourced booking, edit the event directly in Google Calendar.
