All pagesGoogle Calendar

Google Calendar

With the Google Calendar integration, events in the Google Calendar linked to each unit are imported into Werp™ as read-only bookings, and Werp™ bookings can be written out to Google Calendar. Events from 7 days back to 60 days ahead are imported. If you edit an event that Werp™ wrote in Google Calendar, the change does not come back to Werp™.

Werp™ is free for up to 3 members and 50 items, with no credit card required. Get started free

View full documentation

Setting up the integration

Who can do thisAdmin

Only admins can set up the integration. A Google account is connected per workspace, and you can connect several accounts. The events that are read and written are those of the Google Calendar linked to each unit.

1
Open the settings
Open “Settings” → “Integrations” to see the Google Calendar connection and its bindings.
2
Connect a Google account
Click “Connect Google Account” and allow access on Google's screen. The connected account appears under “Connected Accounts”.
3
Add a binding
Click “Add binding” and choose an “Equipment unit” and a “Google Account”. Once you pick an account, its calendars load automatically.
4
Choose a calendar
Under “Google Calendar”, choose the calendar to link. You can't write to a calendar marked “(read-only)”.
5
Choose the sync direction
Turn “Read from Google” and “Write to Google” on or off. By default only reading is on. After adding a binding, you can still switch them with the “Import” and “Export” arrows in the list.
6
First import
Click the refresh icon (“Sync now”) in the list to import right away. Even if you don't, events are imported at the times described under “When events are imported” below.
The “Integrations” screen. It lists the connected Google account and the bindings between units and calendars. Each binding shows its import and export direction and when it last synced.
You can link several calendars to one unit. Importing reads from every calendar that has reading on. A new booking is written to just one calendar: the one with writing on that was linked first (there's no screen for choosing it). It's clearest to turn writing on for only one calendar per unit.

Read: Google Calendar → Werp™

For bindings with reading on, events in the Google Calendar are imported as bookings for that unit.

  • Events from 7 days before to 60 days after the time of the import are covered. At most 500 are imported at a time.
  • Imported events become Confirmed bookings and, like Werp™ bookings, count in the overlap check. They can't be edited, deleted, picked up or returned from Werp™. The overlap check is not run at import, so an event that overlaps a Werp™ booking is imported anyway and both stay.
  • The booking title is the event title. The borrower field shows the event's organizer, or the creator if there is none, or “Google Calendar” if neither exists. The event description goes in the note.
  • If you change an event's time or title in Google Calendar, the Werp™ booking changes the same way at the next import.
  • If you delete or cancel an event in Google Calendar, the Werp™ booking becomes Cancelled at the next import and no longer counts in the overlap check.
  • Events that Werp™ wrote are not imported, even if the same unit has that calendar linked for reading. A booking is never duplicated on the same unit. The exception is an event left in Google Calendar after its booking was deleted (see the warning below): the next import brings it in as a booking.

When events are imported

Importing doesn't run all the time. It runs on these triggers:

TriggerCondition for importing
When a list of bookings is shown, such as the “Bookings” pageBindings last imported 5 minutes ago or more are imported. The page waits up to 3 seconds; anything not finished is left for the next opportunity.
When the kiosk screen refreshes automatically (every 60 seconds)Of that unit's bindings, those last imported 5 minutes ago or more are imported (it waits up to 6 seconds).
When you click “Sync now” in the listThat binding is imported right away. The same binding can be synced at most once every 30 seconds.
The hourly automatic jobBindings not imported for 50 minutes or more are imported, oldest first, up to 20 per run. It runs even when nobody has a screen open.

So if nobody has the screen open, an event you add in Google Calendar can take up to about 2 hours to show up in Werp™. If you're in a hurry, click “Sync now”.

Write: Werp™ → Google Calendar

For bindings with writing on, that unit's Werp™ bookings are written to Google Calendar as events. The event title is the booking title, and the description contains the borrower, item, note and a link to Werp™. Writing is triggered as follows:

Action in Werp™Event in Google Calendar
Creating a booking (including group bookings, adding an item to an existing booking, and bookings made on the kiosk)It is created. A booking that needs approval is created once it is approved (bookings awaiting approval or declined aren't written).
Editing a booking (date and time, title, borrower, etc.), and extending or ending now on the kioskIt is updated.
Cancelling or deleting a bookingIt is deleted.
Moving a booking to a different unitIt is deleted from the original unit's calendar and created in the new unit's calendar.
Recording a pickup or returnNothing happens. The event stays as it is.

Bookings that existed before you turned writing on are also written, if they start less than 24 hours ago or later (Cancelled ones excluded). The hourly job writes 20 at a time. Bookings imported from Google Calendar are not written.

Werp™ remembers, for each booking, which calendar it wrote the event to. Editing, cancelling or deleting that booking updates the event in that same calendar, even if you later turn writing on or off for other calendars. Bookings written before this was introduced (before 8 October 2026) have no record, so they go to the calendar with writing on that was linked first. Once such a booking has been updated successfully, its calendar is recorded from then on.

When you turn writing off for the calendar a booking was written to
Edits and deletions of that booking no longer reach Google Calendar, and Werp™ doesn't write them to another calendar instead. The same applies when you disconnect the account. Turn writing back on and the next edit reaches it again. If you delete the booking while writing is off, the event stays in Google Calendar, and turning writing back on doesn't remove it. Delete it in Google Calendar by hand.

When writing fails

  • A booking whose event could not be created is created again by the hourly job (for bookings that start less than 24 hours ago or later).
  • When updating or deleting an event fails, it is recorded and the hourly job retries up to 8 times. If it is still pending after 7 days, it is discarded.
  • If Google refuses because you lack write permission, writing for that binding is turned off automatically and a warning icon appears on “Export” in the list. Re-link to a calendar you own or fix the calendar's permissions, then turn it on again.
Changes made in Google Calendar don't come back to Werp™
If you move or delete an event Werp™ wrote, in Google Calendar, the Werp™ booking doesn't change. Make booking changes in Werp™. Werp™ doesn't resolve events that overlap each other inside Google Calendar.

Disconnecting and deleting a binding

ActionResult
“Disconnect” an accountBindings that use that account stay in the list, but importing and writing stop. Bookings already imported aren't removed; they stay without being updated and keep counting in the overlap check.
Delete a binding (trash icon in the list)It is deleted immediately, without a confirmation. All bookings imported from that calendar become Cancelled and no longer count in the overlap check.

In both cases, events Werp™ has already written to Google Calendar are not deleted. If you disconnect an account and want to avoid imported bookings blocking slots, delete the binding too.

Use case scenarios

Video production team
Camera bookings appear automatically in the team's shared Google Calendar. Without opening Werp™, the director can check “Axeon M7 IV: Alex, Thu–Fri” alongside the crew call and the location scout.
Conference room management
A meeting room's projector is linked to that room's Google Calendar. When someone adds “Board meeting, 2:00–4:00 pm” to Google Calendar, Werp™ imports it. After that, trying to book the projector in that time slot is stopped as an overlap.
Zero-friction team adoption
Most members don't have to change how they work. Equipment bookings show up automatically in the calendar they already look at every morning. Seeing “Projector: Maria, Wednesday” tells them the projector is in use. No chat and no Werp™ account needed.
Kiosk: bookings from Google Calendar can't be extended or ended
When the booking in use on the kiosk is a Google Calendar event, “Extend” and “End now” aren't shown. A change made in Werp™ would be reverted to the Google Calendar content at the next import. To extend or end it, edit the event directly in Google Calendar.
Was this page helpful?

Ready to get started?

Sign up for free. No credit card required.

Create your workspace