Calendar & Channel Sync

Airflow Integrated — One calendar for all your bookings. Publish one availability feed your channels can read, and cut down on double-bookings.

The double-booking problem

If you list on multiple platforms — Airbnb, Booking.com, your own website — keeping availability in sync is a constant worry. A guest books on Airbnb while another books the same dates on your website. Now you have a problem, an awkward conversation, and a potential bad review.

Airflow helps by consolidating all bookings into one calendar and publishing a single availability feed that your other platforms can import. Note that OTAs like Airbnb and Booking.com refresh imported iCal feeds on their own schedule (typically every few hours), so cross-platform availability is kept current on their refresh cycle rather than instantly — but you finally have one authoritative calendar feeding them all.

How calendar sync works

Bookings flow in

Every booking that enters Airflow — whether from a forwarded OTA email, a direct website booking, or a manual entry — is added to your unified calendar. Each booking shows:

Guest information (without exposing names on shared feeds for privacy)
Check-in and check-out dates
Source platform (Airbnb, Booking.com, Direct, etc.)
Booking status (confirmed, pending, cancelled)
Number of nights and guest count
Booking value

Availability flows out

Airflow generates iCal feeds for each resource that you can import into any platform:

Full feed (for your own use) — includes booking details like provider, confirmation code, nights, guest count, and value
Blocked feed (for sharing with OTAs) — shows only "Not available" blocks, keeping your booking details private

These feeds also include:

Manual availability blocks (maintenance periods, owner stays)
Turnaround/buffer days between bookings
Events imported from connected calendars

Google Calendar & Outlook integration

For a richer experience, connect Google Calendar or Outlook Calendar directly:

Push (Airflow to Calendar)

Each booking creates a calendar event with:

Summary: "Booked — [Platform] ([Confirmation Code])"
Description: guest count, number of nights, booking value
Correct start/end dates and times

Pull (Calendar to Airflow)

Events from your calendar are imported into Airflow's calendar_events_raw table. This means:

Personal blocks you add in Google Calendar appear as unavailable in Airflow
Events from other calendar feeds (e.g., another PMS) are captured
Everything contributes to the single source of availability truth

Deduplication

Airflow tracks which bookings have been synced via a booking_calendar_links table. This prevents duplicate calendar events when bookings are updated or re-synced.

Multi-resource management

If you manage multiple properties, each resource gets its own:

Calendar view in the portal
iCal feed URL (full and blocked versions)
Google/Outlook calendar connection

Availability is managed per-resource, so there's no cross-contamination between properties.

Setting up calendar sync

iCal feeds — available immediately. Copy your feed URL from the resource settings and paste it into your OTA's calendar import
Google Calendar — connect from the Connections page, select which calendar to sync with, and bookings start appearing
Outlook Calendar — same process as Google Calendar

Google and Outlook calendar sync runs bi-directionally and checks for updates regularly. iCal feeds you paste into OTAs are pull-based — those platforms re-read your feed on their own refresh schedule.

Buffer days

You can configure turnaround days between bookings — time for cleaning, maintenance, or simply a breather. These buffer days appear as blocked on your calendar feeds, preventing back-to-back bookings that don't leave enough preparation time.