Connect a Google Calendar

If you track availability or tours in Google Calendar, you can sync it into Rezi the same way you connect any iCal feed.

This is the connector for everything that doesn’t live on a booking platform: the family’s lake-house weekends you keep in a shared Google Calendar, renovation windows your contractor emails you, tentative holds you haven’t committed to a platform yet. If it’s an event on a Google Calendar, Rezi can treat its dates as blocked, which keeps the AI from offering a weekend you promised to your in-laws.

1. 1

   Get the iCal address

   In Google Calendar → Settings → your calendar → “Secret address in iCal format,” copy the URL.

2. 2

   Add it to the building

   Paste it into Properties → [building] → Calendars.

3. 3

   Wait for the first sync

   Rezi imports the busy blocks and refreshes on the usual cycle.

Secret address vs. public address

Google offers two iCal links per calendar, and the difference matters. The public address only works if you’ve made the whole calendar public, usually wrong for personal calendars. The secret address works without making anything public: it’s a long, unguessable URL that grants read access to whoever holds it. That’s what you want for Rezi, and it’s also why the warning below exists, the URL itself is the key, so it belongs in Rezi and nowhere else.

Use a dedicated calendar, not your main one

The strongest pattern: create a Google Calendar specifically for the property (“Lake House blocks”), share it with whoever needs to add holds, your spouse, your co-host, and connect that to Rezi. Connecting your main personal calendar technically works, but then every dentist appointment becomes a property block, since Rezi conservatively treats all events on the feed as unavailable dates. A dedicated calendar keeps the meaning of “event = property blocked” clean, and gives non-Rezi users (family, cleaners) a familiar way to block dates that flows straight into the AI’s answers.

How it fits the bigger picture

A connected Google Calendar is a feed like any other: its blocks join the merge, they’re included in Rezi’s export to your booking platforms, and they obey the same 15-minute refresh. For one-off blocks, a manual block inside Rezi is quicker; the Google Calendar route earns its keep when other people need to create blocks, or when the schedule already lives in Google and you’d rather not maintain it twice.