Connecting your Google Calendar tells Mucka who you are on Google's side. Once the sync engine ships, your Mucka jobs and appointments will land in your Google Calendar automatically and any changes either side will keep both in step.
Heads up: the connection is live today, the actual sync is shipping in a follow-up. Connect now and Mucka starts syncing the moment the engine goes live, no extra step needed.
Connect your account
Head to Settings → Integrations → Google Calendar and tap Connect.
Google asks you to sign in and grant Mucka access to your calendar. The permissions you're granting:
- See and edit events on all your calendars (so Mucka can write new jobs in)
- Your email address and basic profile (so Mucka can show "Connected as ryan@gmail.com")
Approve and Google sends you back to Mucka with a "Connected" confirmation.
Personal vs work Google accounts
Mucka works with both:
- Personal Gmail (your own calendar)
- Google Workspace (your business calendar if you use Google for work)
Connect whichever calendar you want your Mucka jobs to appear in. Most engineers connect their work calendar so their team can see what they're booked on.
Each engineer connects their own
Calendar connections are per-user. Every engineer connects their own Google account. The owner doesn't connect everyone, each person picks their own calendar.
The owner can see (in their own Integrations tab) which engineers have connected, and disconnect them if needed for offboarding.
What's coming when sync goes live
Once the sync engine ships (next release or two), expect:
- Mucka jobs → Google Calendar automatically as you schedule them
- Google Calendar changes → Mucka when you reschedule or cancel in Google
- Cancel in one, cancel in both so you don't end up double-booked
- Time off / unavailable blocks flow both ways
We'll write the full sync article when it ships. For now, just connecting is enough to be ready.
Disconnect any time
Same page has a Disconnect button. Tapping it:
- Removes Mucka's access to your Google Calendar
- Deletes the stored tokens from Mucka
- Stops any syncing immediately (once sync is live)
- Doesn't delete any events that were already synced
Reconnect any time by going through the Connect flow again.
Common gotchas
- "This app isn't verified" warning from Google. Tap Advanced then Go to Mucka (unsafe). Mucka is verified with Google, but Google sometimes shows this warning for newer scopes. Safe to proceed.
- "Needs calendar permission" after connecting. On the Google screen there's a tick-box for "See, edit, share and permanently delete all the calendars". If it's left unticked, Mucka can sign you in but can't write jobs to your calendar, so nothing syncs. Tap Reconnect and make sure that box stays ticked.
- Connected the wrong account. Disconnect and reconnect, Google will prompt you to pick again.
- Workspace admin blocks third-party apps. If you're on a managed Google Workspace, your admin might need to allow Mucka. Send them the help URL and they can whitelist the OAuth client.
- Token expired showing in the status. Tap Reconnect to refresh, takes 10 seconds.