Skip to main content
Connect Google Calendar to keep your work in sync with the calendars you already live in. It’s set up per user, so each team member connects their own Google account. Find it under Settings then Integrations then Google Calendar.

​
What syncs, and which way

ShineCRM pushes your work out to Google, and reads busy times in:
  • Out to Google: your jobs (written to each assigned person’s calendar, updated through the job’s life, and removed if it’s cancelled), your published shifts, and your calendar events (appointments).
  • In from Google: busy blocks only. Events on the calendars you choose show up as unavailable time in the ShineCRM calendar and scheduler, so you don’t get double-booked.
This is one-directional for your records. ShineCRM writes appointments, jobs, and shifts to Google and reads busy times back. Edits you make inside Google Calendar do not become ShineCRM jobs or events. Treat ShineCRM as the source of truth.

​
Connect and configure

Connect your Google account, then set three controls (they autosave):
  • Block as busy: pick the Google calendars whose events should appear as unavailable time in ShineCRM.
  • Push appointments to: choose which calendar receives your jobs and events, or “None” to not push.
  • Push shifts to: choose which calendar receives your published shifts, or “None.”
A sync health card shows the last sync and any recent errors, with a Sync now button to force one. If Google access expires, you’ll see a reconnect prompt.

​
Disconnect

Disconnecting stops future syncing. Events already written to Google stay where they are; they aren’t deleted.

​
Frequently asked

Can different team members use different Google accounts? Yes. Each person connects their own, so the dispatcher’s calendar and a crew member’s calendar can be entirely separate Google accounts. If I change a job in Google, does ShineCRM update? No. Changes flow from ShineCRM to Google, not back. Make job changes in ShineCRM. What happens to my Google events if I disconnect? They stay. Disconnecting only stops new syncing; it doesn’t remove what’s already there.