Can a Timer Process Booking Requests Before Cutoff?

Use n8n Schedule Trigger for deadline-driven batches. Compare immediate intake with polling for meeting requests, and recheck Google Calendar availability before creating any event.

Measure how much of the booking window polling consumes

n8n Schedule Trigger supports fixed intervals and uses the workflow timezone when set. Set that timezone explicitly, publish a staging workflow, and log the request arrival and the time the booking step actually evaluates it. Test an arrival just after a poll as well as one on the boundary. In an illustrative workflow that polls every 15 minutes and needs three minutes for review, a request received at 09:16 becomes eligible at 09:30 and reaches the availability check at 09:33. If the meeting starts at 09:40 with a ten-minute booking cutoff, polling has already missed the deadline. Immediate intake with the same review delay reaches the check at 09:19. Test wall-clock schedules separately around local clock changes and record the actual fire times in UTC so a repeated local hour is easy to diagnose.

Schedule Trigger | Nodes | n8n Docs

Use a staging calendar to test the booking race

Google Calendar Freebusy queries availability for a set of calendars. Treat the result as a snapshot and test the interval between reading it and creating an event. Send two synthetic requests for overlapping times, insert a conflicting event between the first lookup and the booking decision, and retry one request with the same request ID. At decision time, check the relevant calendars again and route writes through a shared booking coordinator that serializes overlapping requests for each resource. Keep the request ID with the booking outcome so a retry can return the original decision without creating another invitation. Measure the time spent waiting for that coordinator alongside review delay. A successful test records at most one accepted event for the overlapping interval and at most one event per request ID. External calendar writers can still race after the final check.

Freebusy  |  Google Calendar  |  Google for Developers

Give the timer a deadline

Use n8n’s Schedule Trigger for a deliverable that is due even when nobody asks for it. Add a trigger rule for the agreed cadence, set the workflow timezone explicitly, then save and publish. For the first scheduled run, send the output to a test destination and record the expected start, actual start, and completion time. Choose a runtime that will be available at the scheduled hour.

Define what a late run should do before enabling delivery. A morning brief might still be useful ten minutes late and misleading after lunch. Choose a cutoff, record skipped work, and give each scheduled occurrence a stable identifier so a retry can check whether it already delivered the brief.

Schedule Trigger | Nodes | n8n Docs

Make availability an input to booking

For a meeting request, capture duration, required attendees, the acceptable date range, and the requester’s timezone. Ask for any missing detail that could change the proposed time. Google Calendar’s free/busy query supplies availability for a set of calendars. Intersect the returned busy intervals with the requested hours, treating unavailable calendar data as unknown. Offer only slots that fit the full duration and all known constraints.

Present the exact start, end, timezone, and invitees for confirmation. Recheck availability immediately before creating the event and record the returned event identifier after success. A recheck narrows the window for a conflict. If a slot has become busy, return new options and ask the requester to choose again.

Freebusy  |  Google Calendar  |  Google for Developers

Test what changes after a proposal

In an illustrative test, an n8n workflow publishes a draft at 9:00 a.m. America/New_York each weekday. Set that timezone on the workflow so the instance setting cannot silently determine the hour. Suppose the draft suggests Tuesday at 2:00 p.m. for a 30-minute call, a guest selects it at 10:05 a.m., and another event has occupied that slot since 9:45 a.m.

A passing test produces one draft at the scheduled hour, zero invites from the timer, and a fresh proposal when the guest selects the occupied slot. On a second attempt with an open slot, expect exactly one calendar event. Submit the same confirmation again and check that the booking step returns the existing result without creating a second event.

Schedule Trigger | Nodes | n8n Docs

Pilot direct booking on a test calendar

Schedulebot documents Google Calendar availability checks and event creation in the same integration. If you want guests to book directly, start with a dedicated test calendar and define the hours, meeting lengths, and guest eligibility your operator policy will allow. Verify where those rules are enforced before connecting a calendar that contains real commitments.

Submit two requests for the same slot and inspect both replies and the calendar. A pass leaves one event and gives the second guest a truthful status. Also test a response timeout after event creation. If your integration cannot reconcile the original write, send the request to an operator for review before trying again. Direct booking saves a confirmation round trip with the owner, while a mistaken write can require a correction to every invitee.

GitHub - anthroos/open-schedule-agent: Open-source AI scheduling agent — your own Calendly with conversational AI · GitHub

Sources