Syncing with Google Calendar

Syncing with Google Calendar

You live in your personal calendar. TrailerBase pushes your reservations to your Google Calendar so pickups and returns sit alongside the rest of your day.

The connection is outbound only — TrailerBase writes events to Google but never reads from Google. Changes you make in Google itself do not flow back to TrailerBase.

Connecting Google Calendar

1. Open the Calendar page in TrailerBase.
2. Click the Calendar Sync chip in the page header.
3. Click Connect Google Calendar and approve the permission prompt.

Reservations push to your primary Google calendar.

Once connected

• Creating a reservation in TrailerBase pushes an event to your Google calendar within a few seconds.
• Editing dates, trailer, or renter on a TrailerBase reservation updates the matching Google event.
• Cancelling a reservation removes the Google event.

What you see in Google

Each TrailerBase reservation appears as an event with:

• Title: "[Trailer name] - [Renter name]"
• Start: Pickup date/time
• End: Return date/time
• Location: Your business address or delivery address
• Notes: Reservation ID, total, phone number, and a deep link back into TrailerBase

Backfilling existing reservations

If you connected after you already had reservations in TrailerBase, click Sync now in the Calendar Sync drawer. TrailerBase pushes every eligible reservation to your Google calendar in a single batch. Re-running is safe — each reservation is matched by its TrailerBase ID, so existing Google events are updated rather than duplicated.

Disconnecting

Click Disconnect in the Calendar Sync drawer. The Google-side events remain in Google as a snapshot but stop updating.

Troubleshooting

• "Reconnect required" badge — Your Google token expired or was revoked. Click the chip and reconnect.
• Events not showing up — Confirm the Google account you connected is the one you're looking at, and that the chosen calendar is enabled in Google's left sidebar.
• Duplicate events — Rare. If you see them, disconnect and reconnect; the system rebuilds the link by reservation ID and dedupes on the next push.