Google Calendar Sync

Calendar Sync writes each property's bookings and availability blocks into a Google Calendar you already use, and keeps that calendar current as reservations come and go. It is a one-way copy: Argonautas writes to Google, and nothing on the Google side ever changes a booking back in Argonautas.

It replaces the old per-property iCal subscription. An iCal feed only refreshes when Google decides to re-poll it, which can leave the calendar hours or days stale. Calendar Sync pushes each change to Google directly, so the calendar reflects a new booking or a cancellation within minutes.

What Shows on the Calendar

For each mapped property, Argonautas creates an all-day event for:

• Every booking -- the stay is drawn from arrival day through the night before departure, so the checkout day is left open for the next guest (the vacation-rental standard). The event carries the guest name and stay details.
• Every availability block -- owner stays, maintenance holds, partner blocks, and manual "unavailable" ranges, whatever the reason a night is off the market. This means the Google Calendar shows the complete occupancy picture, not just guest reservations.

A booking that is still tentative (pending, on hold, or awaiting a partner's confirmation) is written with a "TENTATIVE" label so you can tell it apart from a confirmed stay at a glance. When a booking is cancelled, marked a no-show, or declined by a partner, its event is removed from the calendar.

A note on guest data. Calendar Sync writes the guest's name and stay details into the Google Calendar event. Anyone with access to that Google Calendar can see them. Map properties to a calendar only the right people can view.

Before You Start

Calendar Sync connects to Google, so you will need:

• A Google account whose calendars your team already uses for these properties.
• Permission to grant Argonautas access to that account's calendars during the one-time connection step.

The connection is managed for the whole company, so one authorized account can serve every property. You can also connect more than one account if different homes live on different Google accounts.

Step 1 -- Connect a Google Account

1. Go to Settings and find the Google Calendar card.
2. Click Connect. You are redirected to Google's sign-in and consent screen.
3. Choose the account and approve the requested calendar access. Google returns you to Settings, and the card now shows the account with a Connected badge.

To add another account later, use Connect another account on the same card. Each connected account can be removed with Disconnect (you'll be asked to confirm). Disconnecting removes Argonautas's access and cleans up the events it wrote through that account.

If the card shows an account with a needs reconnect note, its access has expired or been revoked on the Google side. Click Connect again to restore it.

Step 2 -- Map a Property to a Calendar

A connection authorizes an account; a mapping decides which calendar a specific property writes to. You create mappings on each property, not on the Settings card.

1. Open the property and find its Calendar Sync card.
2. Choose the connected Google account.
3. Choose the calendar on that account that this property should write to.
4. Leave Active checked and click Save.

The property's bookings and blocks are written to that calendar from then on. If no account is connected yet, the card points you back to Settings instead of showing an empty dropdown.

Use Resync on the card at any time to force a full rewrite of that property's events (useful right after you first map it, or if you ever suspect the calendar has drifted). Last synced shows when the property last wrote to Google.

Step 3 -- Review Every Mapping in One Place

Back in Settings, the Google Calendar section includes a mapping table listing every property that syncs, the account and calendar it writes to, its status, and when it last synced. From here you can:

• Pause a mapping to stop writing new changes without deleting it, and Resume it later.
• Resync a property on demand.

New mappings are still created from the property card; this table is the company-wide overview and the place to pause, resume, or audit them.

Blocking the Checkout Day (Company Setting)

By default, a booking's band ends the night before departure, leaving the checkout day open. Some operators prefer the departure day to also read as blocked on the calendar (for example, to reserve it for turnover cleaning).

The Block the checkout day toggle on the Google Calendar card applies this preference company-wide. When on, each booking's all-day band is extended one day so the checkout day shows occupied too.

This toggle changes only how stays are drawn on the Google Calendar. It does not touch real availability, pricing, minimum stays, or anything sent to the OTAs. A night that is genuinely bookable stays bookable.

How Changes Reach the Calendar

• Most changes appear within minutes. Creating, editing, or cancelling a booking, and adding or removing a manual or imported-iCal block, pushes to Google right away.
• A nightly refresh catches everything else. Once a day, Argonautas reconciles each mapped property against Google over a wide date window (roughly a month back and well over a year forward), correcting any drift and picking up bulk changes such as blocks synced from a connected external system. If a realtime update is ever missed, the nightly pass repairs it.

You never have to trigger this by hand, but Resync is there when you want an immediate full refresh.

Key Concepts

• One-way sync -- Argonautas writes to Google Calendar. Edits made directly in Google Calendar are not read back and will be overwritten on the next sync.
• Connection -- An authorized Google account, managed for the whole company on the Settings card. Several are allowed.
• Mapping -- The link between one property and one calendar on a connected account. Created and managed on the property's Calendar Sync card.
• Active vs. Paused -- A paused mapping keeps its configuration but stops writing new changes until you resume it.
• Block the checkout day -- A company-wide display preference that extends each stay's band by one day on the calendar only.

Common Questions

Does editing an event in Google Calendar change the booking in Argonautas? No. Sync is one-way. Any manual edit in Google Calendar is cosmetic and will be replaced the next time that booking or block syncs. Make the change in Argonautas.

Can two properties share one calendar? Yes. Map each property to the same calendar and both sets of events appear on it. Each event is labelled with its property.

I connected an account but nothing appears on the calendar. Connecting an account is only step one. You also have to map each property to a specific calendar on that account. Check the property's Calendar Sync card, then use Resync.

Why is a stay showing one day shorter than I expected? That is by design: the checkout day is left open so the home reads as available for the next arrival. If you want the departure day blocked too, turn on Block the checkout day.

What happens when I disconnect an account? Argonautas stops writing through it and removes the events it created via that account. Your bookings and blocks in Argonautas are untouched; only the Google Calendar copy is cleaned up.

Do owner stays and maintenance holds show up, or just guest bookings? Both. Every availability block syncs, regardless of why the night is blocked, so the calendar reflects true occupancy.

Related

• Availability -- Managing bookings and availability blocks that feed the calendar.
• Settings Overview -- General settings and configuration.
• Distribution Channels -- How OTA channels (a separate system) keep availability in sync.