Jobber and Google Calendar: what syncs, what imports, and what to verify

The short answer

A Jobber calendar subscription shows selected Jobber items in Google Calendar. It is one-way: a personal Google event does not return to Jobber as occupied time. Importing upcoming Google events as jobs is a separate, one-time operation. Neither route proves that online booking will avoid a personal conflict. Keep Jobber as the operational schedule and verify last-minute changes there before a field departure. Jobber's calendar-sync documentation explains the direction and refresh behavior; its import guide describes a different operation.

Choose the operation before connecting anything

The official online-booking guide describes availability from the team's Jobber schedule and settings. It does not turn the outward subscription into a reverse availability feed. Ask which schedule staff must check before approving a booking, especially if personal commitments live outside Jobber.

Know the documented boundaries

Jobber says the subscription is configured on Jobber.com, with selectable item types and assignment scope. Its initial feed covers two weeks back and 20 weeks ahead of initiation. Updates are not real time; the guide says Google pulls roughly every 12 hours and offers no manual Google refresh in this setup. That figure is vendor guidance, not our measurement or a service-level promise. Keep the feed URL private because it is a route into your schedule; do not paste it into a public calendar, shared document, or support screenshot.

By contrast, the import documentation limits candidates to the next two months, excludes past events and reads the primary Google calendar. Jobber requests temporary read-only access to Google, then may create jobs, clients and properties in Jobber. A candidate needs a client name, address and service indication; some events can be rejected. A repeated import can still produce duplicates. Read-only describes the Google access, not a prohibition on creating Jobber records. Review permissions and the import summary before any authorized migration; do not use reimport as a refresh button.

Copy a source-to-destination comparison row

Use synthetic records in a permitted test environment. Never put a real customer, private feed URL or token into a public worksheet. The blank actual result is deliberate: the checks below have not been run by ServiceTech Signal.

For example, a fictional technician moves DEMO-VISIT-25 from 09:00 to 10:00 in Jobber while a Google view still shows 09:00. That is a risk scenario, not something we observed. The next action is to verify the live source schedule and tell the relevant person directly, not to infer that the older display is an appointment confirmation.

Seven proposed checks before relying on the second view

Optional, only with explicit authorization to create import records: place distinct synthetic job-like events on a primary and a secondary Google calendar, verify the two-month scope and required fields, run the import once, and inspect accepted and rejected items and any duplicates. Do not run this on production customer calendars just to validate a guide. A subscription horizon test and an import scope test measure different boundaries.

Before someone leaves for a job

Have one person check the operational Jobber visit for the current time, assignment and status. Compare the synthetic or authorized record ID, date, named zone and offset to the secondary display. If a same-day edit has not appeared in Google, tell the affected person through the team's normal direct channel and record acknowledgment. Do not wait for a forecast refresh time as if it were a guarantee. If the calendars disagree, pause the departure decision until the source record and responsible dispatcher agree.

If all a small team needs is a second visual reference, it can use the subscription with that limitation or simply consult Jobber directly. For the wider product decision, read our Jobber review and controlled workflow protocol. If the goal is to move an entire system, use the separate migration checklist. No new connector or affiliate relationship is required by this worksheet.