Teams whose working day is already in Outlook — consultants, clinics, surveyors, anybody on Microsoft 365 — who want to publish a booking page without it selling time that is already spoken for.
Your team's busy time is read straight from Outlook Calendar, so a public booking page never offers an hour somebody is already committed to.
Matched per person by email address. If the calendar can't be reached the times stay on screen rather than the page emptying — it fails open, deliberately.
What it doesn't do: it brings no data into tables — connecting it adds no rows anywhere. There are no automation steps that write back to Outlook Calendar. Anything else you have read about Outlook Calendar and RowFold, this page is the authority: it is generated from the connector's own code.
This connector does one job, and it needs one piece of setup that most people miss. The booking page has to be told which field on your staff table holds each person's Outlook address. Connecting the account on its own changes nothing at all.
You'll know it worked: Block an hour in Outlook for one person, wait two minutes for the cache to turn over, then reload the public page with that person selected. The hour should have gone. Do this once after setup, because a connector that has silently stopped working looks exactly like one that is working.
Mixed estates need no special handling, because availability is worked out per person rather than per workspace. What matters is that each person's address points at the calendar they really use.
You'll know it worked: Block an hour for one person on each provider and confirm both hours vanish from the public page. Anybody with no connected calendar keeps their full rota, which is correct: they are not treated as busy.
A booking page that cannot see Outlook is a booking page that sells hours you do not have. Every internal meeting, every school run blocked out at four, every half-day someone booked in January is invisible to it.
Outlook is consulted at the moment the page works out what to offer. If the hour is taken in Outlook it is not on the page, and nobody had to say so twice.
The usual fix is a second copy of everybody's week, maintained by hand in whatever tool takes the bookings. It works until the first time somebody accepts a meeting and forgets to mirror it, which is generally the same week it was set up.
There is no second copy. Outlook remains the single place a person's time is recorded, and the booking page reads it. Nothing to keep in step means nothing to forget.
Shared team calendars make it worse rather than better, because now one person's availability depends on several calendars and no scheduling tool agrees which of them counts.
Availability is resolved per person, by their email address. One staff member's commitments govern one staff member's slots — a colleague's busy afternoon has no effect on yours.
No, and that is unusual enough to say plainly. Most integrations bring data in or write data out; this one answers a question. Connecting it creates no table, adds no rows, and changes nothing you can look at. The only visible difference is that hours your team is busy stop appearing on your booking pages.
By something not happening, which is the awkward part. The honest test is to block an hour in Outlook and reload your booking page — that hour should be gone. It is worth doing once after connecting, because a connector that quietly stops working looks identical to one that is working perfectly.
The page keeps offering times. Failing the other way would mean a third party's bad minute silently emptying a live booking page, which costs a great deal more than the occasional clash it would avoid. The check is reported as not having run, rather than being treated as though the calendar came back empty.
Not yet. With an Outlook account connected, RowFold reads when your team is busy and nothing else. The customer's confirmation email carries a calendar file they can add to their own diary, and the booking itself is already a record in RowFold that the rest of your automations can act on. A connected Google calendar can receive each booking as an event today, which the Google Calendar page describes.
Both can connect — the sign-in accepts personal and work identities alike. In practice this earns its place on Microsoft 365 work accounts, where the calendar is genuinely the record of somebody's day rather than somewhere to note the occasional dentist appointment, and where colleagues are already booking time in it without asking first.
Yes, and mixed estates are common enough to be worth saying plainly. Availability is resolved per person rather than per workspace, so the two connectors sit side by side without either having an opinion about the other's staff. Each person's own calendar governs their own slots, and anybody with neither connected simply has no calendar consulted.
There is no template to wait for. Type a sentence about what you run and RowFold assembles the tables, links, views and dashboard around it — then you change whatever does not fit.