ACTION_ID: google_calendar_check_out_of_office NAME: Google Calendar: Check Out of Office CATEGORY: Integrations CREDITS: 0 Check one person's Google Calendar for an "Out of office" event on a day or within a time range, and return whether they are away. Built for lead routing: look up the assigned rep's email, then send the lead elsewhere when the rep is out. PREREQUISITE: Google Calendar connection, which the user must create in the Floqer UI (Connections page); an agent cannot. It is separate from the Google Sheets connection. One connected account can check anyone whose calendar it can see at free/busy level or better, which Google Workspace grants to everyone in the same organization by default. People outside that Workspace can only be checked if they share their calendar with the connected account. Confirm the connection exists before configuring. 1. INPUTS email (email, required) Email. The person whose calendar to check, usually the rep the lead is about to be routed to. An invalid address fails the row at dispatch with "A valid email is required". date (date, optional) Date. The day to check, as YYYY-MM-DD. An ISO datetime such as 2026-10-05T09:00:00Z also works; only its written date is used. Leave empty to check today. Any other format fails the row with "Date must be YYYY-MM-DD". start_time (time, optional) Start Time. Start of the range to check, as 24-hour HH:mm (e.g. 09:00). Leave empty to start at midnight. end_time (time, optional) End Time. End of the range to check, as 24-hour HH:mm (e.g. 17:30). Leave empty to run to the end of the day. The day and both times are read in the PERSON'S OWN calendar timezone, not the workflow owner's. "09:00 to 17:00" checks each rep's own working day, wherever they are. With no inputs besides email, the action checks the whole of the person's today. 2. OUTPUTS is_out_of_office (boolean): Is Out of Office. `true` when an Out of office event overlaps the checked day or range. This is the field a routing filter reads. out_of_office_from (date): Out of Office From. Start of the out-of-office period, as an ISO datetime in the person's calendar timezone. When several Out of office events overlap the window, this is the earliest start. Empty when not out of office. out_of_office_until (date): Out of Office Until. End of that period (latest end of the overlapping events), same format. A multi-day absence reports its full span, so this tells you when the rep is back. Empty when not out of office. 3. HOW TO CONFIGURE No options call is needed. Configure Action body (check today): { "inputs": { "email": "{{input.rep_email}}" } } Configure Action body (check working hours on a specific day): { "inputs": { "email": "{{input.rep_email}}", "date": "{{input.meeting_date}}", "start_time": "09:00", "end_time": "17:00" } } Field-by-field: - email Required. A column or upstream output holding the person's email. - date Optional. A fixed YYYY-MM-DD or a column reference. - start_time Optional. Fixed HH:mm or a column reference. - end_time Optional. Fixed HH:mm or a column reference. Must be after start_time. 4. KEY NOTES - ONLY Calendar "Out of office" events count. An all-day "Busy" block, a regular meeting, or a Gmail vacation auto-reply does NOT make a person out of office here. Cancelled Out of office events are ignored. - "Not out of office" is a normal success: `is_out_of_office` comes back `false` and the chain continues. Gate downstream steps on the value with a `filter`. - An unreadable calendar is an ERROR, never a silent `false`, so a lead is not routed to a rep who could not be checked. The row fails with: - "No access to 's calendar..." when the person is outside the connected account's Workspace and has not shared their calendar with it. - "Google Calendar access expired. Reconnect Google Calendar..." when the connection was revoked. - "...granted without calendar access. Reconnect Google Calendar..." when the user unticked calendar access on Google's consent screen. - An empty or inverted range fails the row with "End Time must be after Start Time" (for example end_time 00:00 with no start_time, or a range inside a daylight-saving gap) instead of checking nothing. - One Google API call per row. Rows are paced per connected Google account (10 requests per second), so one customer's large list does not slow another's. 5. WHERE IT FITS IN A WORKFLOW The dominant pattern is an OUT-OF-OFFICE ROUTING GATE: look up the assigned rep, then only hand the lead to reps who are in. ... -> (owner lookup / assignment) "Assigned rep" -> google_calendar_check_out_of_office "Is the rep out today?" -> filter "Rep is available" -> (assign to rep / push to CRM / notify rep) filter: {{.is_out_of_office}} is "false" Rows for reps who are out stop at the filter, with `out_of_office_until` left on the row showing when the rep is back, so they can be reviewed or reassigned from the sheet. To check a future meeting slot instead of today, map the meeting date into `date` and the slot into `start_time` / `end_time`. 6. WHEN TO USE - Route new leads away from reps who are on leave or out today. - Check a rep's availability for a specific day or time slot before booking or assigning a meeting. - Flag accounts whose owner is away so a backup can follow up. 7. WHEN NOT TO USE Finding who owns a lead in the CRM (run this first, then check the owner) -> action-detail/salesforce_lookup_record.txt -> action-detail/attio_lookup_record.txt Checking general free/busy or meeting conflicts: this action only reads Out of office events, not meetings. Last updated: 2026-10-01.