Q360's scheduler is for dispatchers. Calendars are where everyone else lives.
Q360 has a robust built-in scheduler optimized for dispatchers and project managers — skill-based matching, availability tracking, and capacity planning. For field techs, account managers, and executives who work primarily outside of Q360, calendar integration brings that scheduling visibility into their everyday tools. They live in Outlook or Google Calendar like everyone else.
The predictable gap: a tech's job shows up in Q360 but not their phone calendar. Meetings get double-booked. Field staff show up to the wrong site because they didn't see the change. The "when and where" of the business lives in two places and they don't agree.
"We'd love our techs to just look at their calendar" — said by every Q360 shop that hasn't yet wired up a real integration. It sounds simple. Most off-the-shelf tools don't do it well.
Rubi's Advanced Calendar Integration for Q360.
We build a live, two-way-aware sync between Q360's scheduler and Office 365 or Google Calendar, with enough customization that each role sees the right events with the right detail.
Your techs see their jobs in their calendar. Your managers see their team in theirs. Q360 stays the scheduling source of truth — the calendar is just the window.
What the integration does.
- Event sync — Q360 service calls, project schedules, and HR reservations push automatically into each assigned person's connected calendar
- Rich event detail — calendar entries include the job address (with a clickable map link), a deep link back to the Q360 record, and the equipment/work summary
- Live updates — when a job time, location, or assignment changes in Q360, the calendar event updates in place. No duplicates, no stale events.
- Customizable presentation — titles, descriptions, and attendee lists are configurable per event type so service calls look different from project visits or HR reservations
- Low maintenance — once configured, the integration runs without supervision. New hires inherit the sync by joining their calendar account to the integration.
Use cases.
Technology stack.
- Office 365 Graph API for Microsoft calendar integration — works with personal Exchange mailboxes and shared team calendars
- Google Calendar API for Google Workspace deployments, including delegated access for shared calendars
- Q360 API for reading scheduled events, assignments, and change events
- Rubi sync service that polls (or listens to webhooks where available), applies customization rules, and maintains event state across all target calendars
Frequently asked questions.
Primarily one-way (Q360 → calendar). Q360 stays the source of truth for job scheduling. We can optionally configure selective bidirectional sync for specific actions (e.g. a tech accepts or declines a job from their calendar and the status flows back to Q360), available as an advanced option.
Supported. We can sync to personal calendars, team calendars, resource calendars (room reservations for training days), or any combination. Common pattern: individual calendars for techs, plus a "Dispatch Board" team calendar that supervisors watch.
Yes — the integration writes to their actual mailbox/calendar, so they need a valid license. Most shops already have 365 for email anyway, so this is usually a non-issue.