Syncing with Airbnb, Vrbo and Booking.com

Stop two calendars selling the same night. RowFold reads each listing's calendar link so nights booked elsewhere are blocked here, and publishes one of its own so those platforms block nights booked here. Two links, pointing opposite ways Airbnb, Vrbo and Booking.com all work the same way: each listing has a calendar link you can export, and a box where you can import somebody else's. There is no API a host with four cottages can reach — the pair of links is the integration. So there are two jobs, and they are separate. Paste their export link into RowFold and the nights it holds stop being sellable here. Give them RowFold's calendar link and the nights you have taken here stop being sellable there. Do only the first and your own booking page is safe while Airbnb keeps double-selling. Reading theirs On Airbnb: Listing → Availability → Sync calendars → Export calendar. Vrbo and Booking.com have the same thing under a different name. Copy that link and paste it on the Calendars page for the table your bookings live in, choosing which unit it belongs to. Treat the link like a password. Anyone holding it can read every arrival and departure on that listing, and on some platforms the guest's name with them — which is why the page is admin-only and shows only the address's host once saved. A calendar that names no unit closes the whole table for the dates it holds. That is the right shape for bank holidays or a refurbishment, and the wrong one for a single cottage's bookings. Sending yours Publish a calendar view of your bookings table, tick Calendar feed on the share, and paste that .ics address into the platform's import box. The share carries a frozen list of published columns, so a column you add later is never quietly exposed — and because the table is booked by the night, the checkout day is published as the exclusive end the platforms expect. That detail matters: read the other way, every one of your bookings would block an extra night on the changeover day. When a sync stops working Refreshes run about once an hour in each direction, and the platforms set their own pace — treat this as protection against double-booking rather than as instant. Nothing is fetched while somebody is looking at your booking page, so a slow platform never slows your page down. If a link stops working, the nights it last knew about stay blocked — losing a feed must never quietly put sold nights back on sale. After a full day without a successful sync RowFold stops offering that unit publicly and says so on the page, rather than risk selling a night it can no longer vouch for. The Calendars page shows when each one last succeeded and what went wrong. Repeating events in an imported calendar are read once only, and the page says how many it found. No rental platform emits them; guessing at the repeats would block dates nobody ever booked. Tips • Press Sync now straight after pasting a link. It is the fastest way to find out you copied the wrong one, and the error says which rule refused it. • One calendar per listing, named for both — "Airbnb · Seaside Cottage" saves a lot of guessing six months later. • The blocks appear on the Scheduler's stays chart as a hatched band, so you can see what is sold elsewhere next to what is sold here. Good to know • A link that needs a login will not work. Some platforms answer with a sign-in page rather than a calendar; RowFold treats that as a failure rather than as "no bookings", so the nights it already knew about stay blocked. • Adding a calendar to a table with no booking page does nothing — these blocks exist so a booking page cannot sell a night twice. • Pausing or removing a calendar puts its nights back on sale immediately. That is the point of it, but it is worth knowing before you press it. Who can do what • Admins only, because the link on each row is the credential — holding it is enough to read a listing's arrivals and departures. • The full address is never shown again after saving and never appears in the audit trail. Only its host is displayed.