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 writes:

• One event per booking, timed from 3:00 PM on the arrival day to 10:00 AM on the departure day, in your company's time zone. The event title reads Property — Guest name (status), and the description lists the confirmation code, number of guests, check-in and check-out dates, and a link to the booking in Argonautas.
• One all-day event per block for owner stays, maintenance holds, and Other blocks (including ones that come in from a connected system), titled Property — block type, with the reason in the description.

Because each booking is a single timed event, Google's Schedule view shows it on every day of the stay: 3pm on the arrival day, All day on the days in between, and Until 10am on the departure day. On any given day, Google lists departures first and arrivals last, so the checkout morning is visible and the home still reads as free for the next arrival that afternoon.

Partner bookings and partner blocks are not copied to Google. They come from an owner's or partner's own channel and iCal feeds, so copying them would only echo those calendars back (and double up when feeds block each other's dates).

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. Checked-out stays stay on the calendar as history. 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 > Integrations and find the Sync bookings to Google Calendar card.
2. Click Connect Google account. 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. Connect the account 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, go to its Calendar tab, and find the Calendar sync card.
2. Choose the connected Google Account.
3. Choose the Calendar on that account that this property should write to.
4. Leave Sync bookings to this calendar 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 > Integrations, the Property calendar mapping table lists 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.

The "Block the Checkout Day Too" Toggle

The Sync bookings to Google Calendar card in Settings still shows a Block the checkout day too toggle, but it no longer changes anything: bookings are now timed events that already run until 10:00 AM on the departure day, so the checkout morning always shows. You can leave the toggle as it is.

How Changes Reach the Calendar

• Most changes appear within minutes. Creating, editing, or cancelling a booking, and adding, editing, or removing an owner, maintenance, or other 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 Calendar sync card in the property's Calendar tab.
• Active vs. Paused: A paused mapping keeps its configuration but stops writing new changes until you resume it.
• Timed booking event: Each booking is one Google event from 3:00 PM on arrival day to 10:00 AM on departure day, so Google shows it on every day of the stay.

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 Calendar sync card on the property's Calendar tab, then use Resync.

Why does a stay show "Until 10am" on its last day? That's the checkout morning. Each booking runs from 3:00 PM on arrival day to 10:00 AM on departure day, so the departure day shows the guest leaving in the morning while the afternoon stays open for the next arrival.

The events used to be all-day bars. What changed? Bookings are now timed events so Google's Schedule view can sort each day departures first, then guests mid-stay, then arrivals. Blocks are still all-day events. For a fuller day-by-day view with service and request details, concierges can use Turnovers in Argonautas. See Concierge Access & Workflow.

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. Owner stays, maintenance holds, and Other blocks sync as all-day events. Partner bookings and partner blocks are left off, because they already live on the partner's or owner's own calendars.

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.